Forbidden area procedures and connection release management

ABSTRACT

The disclosure relates in some aspects to forbidden area procedures and connection release management for a user terminal (UT). Forbidden area-related procedures include, for example, using a special paging area code (PAC) in conjunction with a forbidden area, defining a location reporting threshold for a UT based on the proximity of the UT to a forbidden area, or using a default paging area code if a service restriction for a UT has ended. Connection release management includes, for example, a UT sending a request to cause the release of a Radio Connection that the UT no longer needs, or a UT sending a Location Indication (e.g., including a flag requesting release of a connection) to release the connection used for location reporting when a UT is done sending the location information and is going to go back to idle mode.

CROSS-REFERENCE TO RELATED APPLICATION(S)

This application claims priority to and the benefit of Indian PatentApplication Serial No. 201641036384, filed on Oct. 24, 2016, the entirecontent of which is incorporated herein by reference.

INTRODUCTION

Various aspects described herein relate to wireless communication and,more particularly but not exclusively, to forbidden area procedures andconnection release management.

A satellite-based communication system may include one or moresatellites to relay communication signals between gateways and userterminals (UTs). A gateway is an earth station having an antenna fortransmitting signals to, and receiving signals from, communicationsatellites. A gateway provides communication links, using thesatellites, for connecting a UT to other UTs or to users of othercommunication systems, such as a public switched telephone network, theInternet and various public and/or private networks. In some aspects, asatellite is an orbiting receiver and repeater used to relayinformation.

Geosynchronous satellites have long been used for communication. Ageosynchronous satellite is stationary relative to a given location onthe earth. However, because geosynchronous satellites are limited to ageosynchronous orbit (GSO), which is a circle having a radius ofapproximately 42,164 km from the center of the earth directly above theearth's equator, the number of satellites that may be placed in the GSOis limited.

As alternatives to geosynchronous satellites, communication systemswhich utilize a constellation of satellites in non-geosynchronousorbits, such as low-earth orbits (LEO), have been devised to providecommunication coverage to the entire earth or at least large parts ofthe earth. In non-geosynchronous satellite-based systems, such as LEOsatellite-based systems, the satellites move relative to a communicationdevice (such as a gateway or a UT) on the ground.

At some point in time, a UT may need to be handed-off to anothersatellite. For example, a UT that in communication with a particular LEOsatellite may need to be handed-off to a different LEO satellite as thesatellites move within their respective orbits. It is desirable toensure that a UT can readily be paged as the coverage for the UT shiftsfrom satellite to satellite. In addition, a UT might not be entitled toservice or might not be able to access service in certain locations(e.g., so-called forbidden areas). It is desirable to properly handleservice rejections, re-connections, and related operations in areas inand around these forbidden areas. Accordingly, there is a need foreffective techniques for managing paging areas, forbidden areas, andconnection signaling.

SUMMARY

The following presents a simplified summary of some aspects of thedisclosure to provide a basic understanding of such aspects. Thissummary is not an extensive overview of all contemplated features of thedisclosure, and is intended neither to identify key or critical elementsof all aspects of the disclosure nor to delineate the scope of any orall aspects of the disclosure. Its sole purpose is to present variousconcepts of some aspects of the disclosure in a simplified form as aprelude to the more detailed description that is presented later.

In some aspects, a method of communication includes determining that auser terminal (UT) is located within a forbidden area, and sending aRadio Connection Reconfiguration message to the UT as a result of thedetermination, wherein the Radio Connection Reconfiguration messageincludes a paging area code (PAC) associated with the forbidden area forthe UT. In some aspects, the method further includes receiving a RadioConnection Release message after sending the Radio ConnectionReconfiguration message where the Radio Connection Release messageincludes a request to initiate a Core Network Control Layer updateprocedure, and initiating the Core Network Control Layer updateprocedure as a result of receiving the Radio Connection Release message.In some aspects, the Core Network Control Layer update procedureincludes sending a forbidden paging area code (PAC). In some aspects,the Radio Connection Release message includes a request to initiate aCore Network Control Layer update procedure. In some aspects, the RadioConnection Release message includes timing information that controlswhen the UT is to attempt reconfiguration. In some aspects, the RadioConnection Release message includes information indicative of theforbidden area.

In an aspect of the disclosure, an apparatus for communication includesa memory and a processor coupled to the memory. The processor and thememory are configured to determine that a user terminal (UT) is locatedwithin a forbidden area, and send a Radio Connection Reconfigurationmessage to the UT as a result of the determination, wherein the RadioConnection Reconfiguration message includes a paging area codeassociated with the forbidden area for the UT.

In an aspect of the disclosure, an apparatus for communication includesmeans for determining that a user terminal (UT) is located within aforbidden area, and means for sending a Radio Connection Reconfigurationmessage to the UT as a result of the determination, wherein the RadioConnection Reconfiguration message includes a paging area codeassociated with the forbidden area for the UT.

In an aspect of the disclosure, a non-transitory computer-readablemedium storing computer-executable code includes code to: determine thata user terminal (UT) is located within a forbidden area, and send aRadio Connection Reconfiguration message to the UT as a result of thedetermination, wherein the Radio Connection Reconfiguration messageincludes a paging area code associated with the forbidden area for theUT.

In some aspects, a method of communication includes receiving locationinformation for a user terminal (UT), determining, based on the locationinformation, a proximity of the UT to a forbidden area, and defining alocation reporting threshold for the UT based on the determination. Insome aspects, the method further includes sending the location reportingthreshold to the UT via a Radio Connection Reconfiguration message. Insome aspects, the location reporting threshold comprises a distancethreshold. In some aspects, the location reporting threshold includes aduration threshold. In some aspects, the determination includesdetermining that the UE is near the forbidden area. In some aspects, thedetermination includes determining that the UE is in the forbidden area.

In an aspect of the disclosure, an apparatus for communication includesa memory and a processor coupled to the memory. The processor and thememory are configured to receive location information for a userterminal (UT), determine, based on the location information, a proximityof the UT to a forbidden area, and define a location reporting thresholdfor the UT based on the determination.

In an aspect of the disclosure, an apparatus for communication includesmeans for receiving location information for a user terminal (UT), meansfor determining, based on the location information, a proximity of theUT to a forbidden area, and means for defining a location reportingthreshold for the UT based on the determination.

In an aspect of the disclosure, a non-transitory computer-readablemedium storing computer-executable code includes code to: receivelocation information for a user terminal (UT), determine, based on thelocation information, a proximity of the UT to a forbidden area, anddefine a location reporting threshold for the UT based on thedetermination. send the location reporting threshold to the UT via aRadio Connection Reconfiguration message.

In some aspects, a method of communication includes determining that aservice restriction for a user terminal (UT) has ended, and conducting amobility operation using a default paging area code (PAC) as a result ofthe determination. In some aspects, the conducting of the mobilityoperation includes initiating a Register procedure, and initiating aRadio Connection without sending any PAC information. In some aspects,the default PAC is excluded from a set of paging area codes used forpaging area update operations. In some aspects, the default PAC is usedbetween a Core Network Control Layer and a Radio Connection Layerinternal to the UT. In some aspects, the default PAC is not sent in anysignaling messages over-the-air.

In an aspect of the disclosure, an apparatus for communication includesa memory and a processor coupled to the memory. The processor and thememory are configured to determine that a service restriction for a userterminal (UT) has ended, and conduct a mobility operation using adefault paging area code (PAC) as a result of the determination.

In an aspect of the disclosure, an apparatus for communication includesmeans for determining that a service restriction for a user terminal(UT) has ended, and means for conducting a mobility operation using adefault paging area code (PAC) as a result of the determination

In an aspect of the disclosure, a non-transitory computer-readablemedium storing computer-executable code includes code to: determine thata service restriction for a user terminal (UT) has ended, and conduct amobility operation using a default paging area code (PAC) as a result ofthe determination

In some aspects, a method of communication includes determining that atrigger condition has occurred at a user terminal (UT), and sending arequest, from the UT, to release a connection as a result of thedetermination. In some aspects, the determination that the triggercondition has occurred includes determining that the UT will enter idlemode after reporting location information for the UT. In some aspects,the method further includes sending the location information for the UT,wherein the location information is sent in conjunction with the requestto release the connection. In some aspects, the determination that thetrigger condition has occurred includes determining that a network hascompleted downloading of satellite transition information. In someaspects, the determination that the trigger condition has occurredincludes determining that the UT has completed sending of locationinformation. In some aspects, the determination that the triggercondition has occurred includes determining that the UT will transitionto idle mode. In some aspects, the determination that the triggercondition has occurred includes determining that a procedure for whichthe connection was established has completed. In some aspects, theconnection is a Radio Connection for the UT. In some aspects, theconnection is a Core Network Interface connection.

In an aspect of the disclosure, an apparatus for communication includesa memory and a processor coupled to the memory. The processor and thememory are configured to determine that a trigger condition has occurredat a user terminal (UT), and send a request, from the UT, to release aconnection as a result of the determination.

In an aspect of the disclosure, an apparatus for communication includesmeans for determining that a trigger condition has occurred at a userterminal (UT), and means for sending a request, from the UT, to releasea connection as a result of the determination.

In an aspect of the disclosure, a non-transitory computer-readablemedium storing computer-executable code includes code to: determine thata trigger condition has occurred at a user terminal (UT), and send arequest, from the UT, to release a connection as a result of thedetermination.

These and other aspects of the disclosure will become more fullyunderstood upon a review of the detailed description, which follows.Other aspects, features, and implementations of the disclosure willbecome apparent to those of ordinary skill in the art, upon reviewingthe following description of specific implementations of the disclosurein conjunction with the accompanying figures. While features of thedisclosure may be discussed relative to certain implementations andfigures below, all implementations of the disclosure can include one ormore of the advantageous features discussed herein. In other words,while one or more implementations may be discussed as having certainadvantageous features, one or more of such features may also be used inaccordance with the various implementations of the disclosure discussedherein. In similar fashion, while certain implementations may bediscussed below as device, system, or method implementations it shouldbe understood that such implementations can be implemented in variousdevices, systems, and methods.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings are presented to aid in the description ofaspects of the disclosure and are provided solely for illustration ofthe aspects and not limitations thereof.

FIG. 1 is a block diagram of an example communication system inaccordance with some aspects of the disclosure.

FIG. 2 is a block diagram of an example of a ground network (GN) of FIG.1 in accordance with some aspects of the disclosure.

FIG. 3 is a block diagram of an example of a satellite of FIG. 1 inaccordance with some aspects of the disclosure.

FIG. 4 is a block diagram of an example of a UT of FIG. 1 in accordancewith some aspects of the disclosure.

FIG. 5 is a block diagram of an example of a user equipment of FIG. 1 inaccordance with some aspects of the disclosure.

FIG. 6 is a block diagram of an example communication system inaccordance with some aspects of the disclosure.

FIG. 7 is a block diagram of another example communication system inaccordance with some aspects of the disclosure.

FIG. 8 is a flow diagram of an example of a process for using a defaultpaging area code (PAC) in accordance with some aspects of thedisclosure.

FIG. 9 is a flow diagram of an example process for obtaining a new PACin accordance with some aspects of the disclosure.

FIG. 10 is a flow diagram of an example process for assigning aforbidden PAC to a UT in accordance with some aspects of the disclosure.

FIG. 11 is a flow diagram of an example a process for where a UTattempts to establish a connection after a service restriction no longerapplies in accordance with some aspects of the disclosure.

FIG. 12 is a flow diagram of an example process where a UT sends aconnection release indication in a location report in accordance withsome aspects of the disclosure.

FIG. 13 is a flow diagram of an example process where a UT requests aconnection release in accordance with some aspects of the disclosure.

FIG. 14 is a flow diagram of an example process for updating a locationreporting threshold in accordance with some aspects of the disclosure.

FIGS. 15A and 15B (collectively referred to as FIG. 15) are a flowdiagram of an example initial attach process in accordance with someaspects of the disclosure.

FIGS. 16A and 16B (collectively referred to as FIG. 16) are a flowdiagram of an example of a PAC reassignment process for a UT inaccordance with some aspects of the disclosure.

FIG. 17 is a flow diagram of another example of a PAC reassignmentprocess for a UT in accordance with some aspects of the disclosure.

FIGS. 18A and 18B (collectively referred to as FIG. 18) are a flowdiagram of another example of a PAC reassignment process for a UT inaccordance with some aspects of the disclosure.

FIGS. 19A, 19B, 19C, 19D, and 19E (collectively referred to as FIG. 19)are a flow diagram of an example handoff process in accordance with someaspects of the disclosure.

FIGS. 20A and 20B (collectively referred to as FIG. 20) are a flowdiagram of an example initial attach process in a forbidden area inaccordance with some aspects of the disclosure.

FIGS. 21A and 21B (collectively referred to as FIG. 21) are a flowdiagram of an example process where a UT in idle mode moves into aforbidden area in accordance with some aspects of the disclosure.

FIGS. 22A and 22B (collectively referred to as FIG. 22) are a flowdiagram of an example process where a UT in connected mode moves into aforbidden area in accordance with some aspects of the disclosure.

FIGS. 23A and 23B (collectively referred to as FIG. 23) are a flowdiagram of an example process where a UT in idle mode moves into aforbidden area in accordance with some aspects of the disclosure.

FIGS. 24A and 24B (collectively referred to as FIG. 24) are a flowdiagram of a forbidden location handling process in accordance with someaspects of the disclosure.

FIGS. 25A and 25B (collectively referred to as FIG. 25) are a flowdiagram of an example process where a UT in connected mode moves into aforbidden area in accordance with some aspects of the disclosure.

FIGS. 26A and 26B (collectively referred to as FIG. 26) are a flowdiagram of an example process where a UT reattempts service after alapse in restriction in accordance with some aspects of the disclosure.

FIGS. 27A and 27B (collectively referred to as FIG. 27) are a flowdiagram of an example connection establishment process in accordancewith some aspects of the disclosure.

FIGS. 28A and 28B (collectively referred to as FIG. 28) are a flowdiagram of an example connection establishment process in accordancewith some aspects of the disclosure.

FIG. 29 is a flow diagram of an example location reporting process inaccordance with some aspects of the disclosure.

FIG. 30 is a flow diagram of an example threshold reconfigurationprocess in accordance with some aspects of the disclosure.

FIG. 31 is a block diagram illustrating an example hardwareimplementation for an apparatus (e.g., an electronic device) that cansupport communication in accordance with some aspects of the disclosure.

FIG. 32 is a flow diagram of an example forbidden area process inaccordance with some aspects of the disclosure.

FIG. 33 is a flow diagram of an example location reporting thresholdprocess in accordance with some aspects of the disclosure.

FIG. 34 is a flow diagram of an example process for requesting locationin accordance with some aspects of the disclosure.

FIG. 35 is a block diagram illustrating another example hardwareimplementation for an apparatus (e.g., an electronic device) that cansupport communication in accordance with some aspects of the disclosure.

FIG. 36 is a flow diagram of an example default PAC process inaccordance with some aspects of the disclosure.

FIG. 37 is a flow diagram of an example connection release process inaccordance with some aspects of the disclosure.

FIG. 38 is a flow diagram of an example default PAC process inaccordance with some aspects of the disclosure.

FIG. 39 is a flow diagram of an example connection reject process inaccordance with some aspects of the disclosure.

FIG. 40 is a flow diagram of an example connection reject process inaccordance with some aspects of the disclosure.

FIG. 41 is a flow diagram of an example connection reject process inaccordance with some aspects of the disclosure.

FIG. 42 is a flow diagram of an example paging area update process inaccordance with some aspects of the disclosure.

DETAILED DESCRIPTION

The disclosure relates in some aspects to communicating paging areainformation for a user terminal (UT). In some aspects, Radio signals areused to provide paging area code (PAC) information. For example, anetwork may send a PAC to a UT via a Radio Connection Reject message ora Radio Connection Reconfiguration message. In some aspects, the PAC maybe a special PAC to be used in conjunction with a forbidden area. Insome aspects, a UT may send its old PAC to the network (e.g., uponrequest or during a PAC update).

The disclosure relates in some aspects to use of a default PAC. Forexample, a camping UT may use a default PAC known by the UT and anetwork to enable the UT to obtain PAC information from the network. Inone use case, a UT that has not yet been assigned a PAC by the networkcan use the default PAC to start a signaling procedure. In response, thenetwork sends a PAC to the UT via signaling (e.g., via a connectionsetup message or a connection reject message). In another use case, a UTmay discard a network-provided PAC and use the reserved PAC upon lapseof a service restriction (e.g., upon the UT leaving a forbidden area).The UT may then use the reserved PAC for a connection re-attemptprocedure.

The disclosure relates in some aspects to UT location reporting. Forexample, a location reporting threshold may be defined for a UT based onthe proximity of the UT to a forbidden area. As another example, anetwork may send a Location Request message to a UT to request the UT'slatest location (e.g., GPS location).

The disclosure relates in some aspects to connection release management.For example, a UT may send a request to cause the release of a RadioConnection that the UT no longer needs. As another example, a UT maysend a Location Indication (e.g., including a flag requesting release ofa connection) to release the connection used for location reporting whena UT is done sending the location information and is going to go back toidle mode. As yet another example, the network may send to the UT aRadio Connection Release message that includes information such as: aduration indication, a Restricted Area Definition, an indication toforce initiation of an update procedure, or any combination thereof.

The disclosure relates in some aspects to connection reject management.For example, the network may send to the UT a Radio Connection Rejectmessage that includes information such as: a new PAC for the UT, arequest for the UT to immediately attempt to reconnect to the network,or a request for an old PAC.

Various aspects of the disclosure are described in the followingdescription and related drawings directed to specific examples.Alternate examples may be devised without departing from the scope ofthe disclosure. Additionally, well-known elements will not be describedin detail or will be omitted so as not to obscure the relevant detailsof the disclosure.

I. Example Satellite System

FIG. 1 illustrates an example of a satellite communication system 100which includes a plurality of satellites (although only one satellite300 is shown for clarity of illustration) in non-geosynchronous orbits,for example, low-earth orbits (LEO), a ground network (GN) 200 (e.g.,corresponding to a satellite gateway or a satellite network portal) incommunication with the satellite 300, a plurality of UTs 400 and 401 incommunication with the satellite 300, and a plurality of user equipment(UE) 500 and 501 in communication with the UTs 400 and 401,respectively.

The satellite 300 can receive signals from and transmit signals to theUT 400, 401 provided the UT 400, 401 is within the “footprint” of thesatellite 300. The footprint of the satellite 300 is the geographicregion on the surface of the earth within the range of signals of thesatellite 300. The footprint is usually geographically divided into“beams,” through the use of antennas (e.g., the antennas may be used tocreate fixed, static beams or may be used to create dynamicallyadjustable beams through beam-forming techniques). A cell may constituteany forward link frequency within a beam. In the case where each beamuses only one frequency, “cell” and “beam” are interchangeable. Eachbeam covers a particular geographic region within the footprint. Beamsmay be directed so that more than one beam from the same satellite 300covers the same specific geographic region. In addition, beams frommultiple satellites 300 may be directed to cover the same geographicregion.

Each UE 500 or 501 may be a user device such as a mobile device, atelephone, a smartphone, a tablet, a laptop computer, a computer, awearable device, a smart watch, an audiovisual device, or any deviceincluding the capability to communicate with a UT. Additionally, the UE500 and/or the UE 501 may be a device (e.g., access point, small cell,etc.) that is used to communicate to one or more end user devices. Inthe example illustrated in FIG. 1, the UT 400 and the UE 500 communicatewith each other via a bidirectional access link (having a forward accesslink and a return access link), and similarly, the UT 401 and the UE 501communicate with each other via another bidirectional access link. Inanother implementation, one or more additional UEs (not shown) may beconfigured to receive only and therefore communicate with a UT onlyusing a forward access link. In another implementation, one or moreadditional UEs (not shown) may also communicate with the UT 400 or theUT 401. Alternatively, a UT and a corresponding UE may be integral partsof a single physical device, such as a mobile telephone with an integralsatellite transceiver and an antenna for communicating directly with asatellite, for example.

The GN 200 may have access to the Internet 108 or one or more othertypes of public, semiprivate or private networks. In the exampleillustrated in FIG. 1, the GN 200 is in communication withinfrastructure 106, which is capable of accessing the Internet 108 orone or more other types of public, semiprivate or private networks. TheGN 200 may also be coupled to various types of communication backhaul,including, for example, landline networks such as optical fiber networksor public switched telephone networks (PSTN) 110. Further, inalternative implementations the GN 200 may interface to the Internet108, PSTN 110, or one or more other types of public, semiprivate orprivate networks without using the infrastructure 106. Still further,the GN 200 may communicate with other GNs, such as the GN 201 throughthe infrastructure 106 or alternatively may be configured to communicateto the GN 201 without using the infrastructure 106. The infrastructure106 may include, in whole or part, a network control center (NCC), asatellite control center (SCC), a wired and/or wireless core networkand/or any other components or systems used to facilitate operation ofand/or communication with the satellite communication system 100.

Communication between the satellite 300 and the GN 200 in bothdirections are called feeder links, whereas communication between thesatellite and each of the UTs 400 and 401 in both directions are calledservice links A signal path from the satellite 300 to a ground station,which may be the GN 200 or one of the UTs 400 and 401, may begenerically called a downlink A signal path from a ground station to thesatellite 300 may be generically called an uplink Additionally, asillustrated, signals can have a general directionality such as a forwardlink and a return link (or reverse link). Accordingly, a communicationlink in a direction originating from the GN 200 and terminating at theUT 400 through the satellite 300 is called a forward link, whereas acommunication link in a direction originating from the UT 400 andterminating at the GN 200 through the satellite 300 is called a returnlink or a reverse link. As such, the signal path from the GN 200 to thesatellite 300 is labeled a “Forward Feeder Link” 112 whereas the signalpath from the satellite 300 to the GN 200 is labeled a “Return FeederLink” 114 in FIG. 1. In a similar manner, the signal path from each UT400 or 401 to the satellite 300 is labeled a “Return Service Link” 116whereas the signal path from the satellite 300 to each UT 400 or 401 islabeled a “Forward Service Link” 118 in FIG. 1.

A controller 122 of the GN 200 generates, uses, and manages paging areainformation, location information, and connection signaling 124 incooperation with a controller 126 of the UT 400 that likewise generates,uses, and manages paging area information, location information, andconnection signaling 128.

For example, functionality for paging area management 130 of thecontroller 122 may perform paging-related tasks (e.g., paging areaupdates) and send the associated paging area information to the UT 400.In response, functionality for paging area management 132 of thecontroller 126 may process the received paging information to assignpaging areas to the UT 400 and perform related operations.

In a complementary manner, the functionality for paging area management132 may perform paging-relates tasks (e.g., paging area updates) sendthe associated paging area information to the GN 200. For example, thefunctionality for paging area management 132 may report current orprevious paging areas allocated to the UT 400. In response, thefunctionality for paging area management 130 may process received paginginformation to reassign paging areas for the UT 400 and perform relatedoperations.

Functionality for location management 134 of the controller 122 andfunctionality for location management 136 of the controller 126 maycommunicate to enable the GN 200 to obtain location information from theUT 400. For example, the functionality for location management 136 maydetermine the location of the UT 400 and send an indication of thislocation to the GN 200. The functionality for location management 134may use the location information, for example, to determine whether theUT 400 is in a forbidden area. The functionality for location management134 may also request the location information from and send locationreporting thresholds to the functionality for location management 136.

Functionality for connection signaling management 138 of the controller122 and functionality for connection signaling management 140 of thecontroller 126 may cooperate to establish and tear down connections usedfor obtaining paging area information, sharing location-relatedinformation, handling operations in forbidden areas, and other purposes.To this end, the functionality for connection signaling management 140may send connection request messages, connection release requestmessages, and other connection-related signaling to the GN 200.Similarly, the functionality for connection signaling management 138 maysend connection reject messages, connection release messages, connectionrequest messages, connection establishment messages, restricted areainformation, and other connection-related signaling to the UT 400.

Other components of the satellite communication system 100 may includecorresponding controllers as well. For example, other GNs, satellites,and UTs (not shown) may include corresponding controllers.

FIG. 2 is an example block diagram of the GN 200, which also can applyto the GN 201 of FIG. 1. The GN 200 is shown to include a number ofantennas 205, an RF subsystem 210, a digital subsystem 220, a PublicSwitched Telephone Network (PSTN) interface 230, a Local Area Network(LAN) interface 240, an GN interface 245, and an GN controller 250. TheRF subsystem 210 is coupled to the antennas 205 and to the digitalsubsystem 220. The digital subsystem 220 is coupled to the PSTNinterface 230, to the LAN interface 240, and to the GN interface 245.The GN controller 250 is coupled to the RF subsystem 210, the digitalsubsystem 220, the PSTN interface 230, the LAN interface 240, and the GNinterface 245.

The RF subsystem 210, which may include a number of RF transceivers 212,an RF controller 214, and an antenna controller 216, may transmitcommunication signals to the satellite 300 via a forward feeder link301F, and may receive communication signals from the satellite 300 via areturn feeder link 301R. Although not shown for simplicity, each of theRF transceivers 212 may include a transmit chain and a receive chain.Each receive chain may include a low noise amplifier (LNA) and adown-converter (e.g., a mixer) to amplify and down-convert,respectively, received communication signals in a well-known manner. Inaddition, each receive chain may include an analog-to-digital converter(ADC) to convert the received communication signals from analog signalsto digital signals (e.g., for processing by the digital subsystem 220).Each transmit chain may include an up-converter (e.g., a mixer) and apower amplifier (PA) to up-convert and amplify, respectively,communication signals to be transmitted to the satellite 300 in awell-known manner. In addition, each transmit chain may include adigital-to-analog converter (DAC) to convert the digital signalsreceived from the digital subsystem 220 to analog signals to betransmitted to the satellite 300.

The RF controller 214 may be used to control various aspects of a numberof RF transceivers 212 (e.g., selection of the carrier frequency,frequency and phase calibration, gain settings, and the like). Theantenna controller 216 may control various aspects of the antennas 205(e.g., beamforming, beam steering, gain settings, frequency tuning, andthe like).

The digital subsystem 220 may include a number of digital receivermodules 222, a number of digital transmitter modules 224, a baseband(BB) processor 226, and a control (CTRL) processor 228. The digitalsubsystem 220 may process communication signals received from the RFsubsystem 210 and forward the processed communication signals to thePSTN interface 230 and/or the LAN interface 240, and may processcommunication signals received from the PSTN interface 230 and/or theLAN interface 240 and forward the processed communication signals to theRF subsystem 210.

Each digital receiver module 222 may correspond to signal processingelements used to manage communication between the GN 200 and the UT 400.One of the receive chains of RF transceivers 212 may provide inputsignals to multiple digital receiver modules 222. A number of digitalreceiver modules 222 may be used to accommodate all of the satellitebeams and possible diversity mode signals being handled at any giventime. Although not shown for simplicity, each digital receiver module222 may include one or more digital data receivers, a searcher receiver,and a diversity combiner and decoder circuit. The searcher receiver maybe used to search for appropriate diversity modes of carrier signals,and may be used to search for pilot signals (or other relatively fixedpattern strong signals).

The digital transmitter modules 224 may process signals to betransmitted to the UT 400 via the satellite 300. Although not shown forsimplicity, each digital transmitter module 224 may include a transmitmodulator that modulates data for transmission. The transmission powerof each transmit modulator may be controlled by a corresponding digitaltransmit power controller (not shown for simplicity) that may (1) applya minimum level of power for purposes of interference reduction andresource allocation and (2) apply appropriate levels of power whenneeded to compensate for attenuation in the transmission path and otherpath transfer characteristics.

The control processor 228, which is coupled to the digital receivermodules 222, the digital transmitter modules 224, and the basebandprocessor 226, may provide command and control signals to effectfunctions such as, but not limited to, signal processing, timing signalgeneration, power control, handoff control, diversity combining, andsystem interfacing.

The control processor 228 may also control the generation and power ofpilot, synchronization, and paging channel signals and their coupling tothe transmit power controller (not shown for simplicity). The pilotchannel is a signal that is not modulated by data, and may use arepetitive unchanging pattern or non-varying frame structure type(pattern) or tone type input. For example, the orthogonal function usedto form the channel for the pilot signal generally has a constant value,such as all 1's or 0's, or a well-known repetitive pattern, such as astructured pattern of interspersed 1's and 0's.

The baseband processor 226 is well known in the art and is therefore notdescribed in detail herein. For example, the baseband processor 226 mayinclude a variety of known elements such as (but not limited to) coders,data modems, and digital data switching and storage components.

The PSTN interface 230 may provide communication signals to, and receivecommunication signals from, an external PSTN either directly or throughadditional infrastructure 106, as illustrated in FIG. 1. The PSTNinterface 230 is well known in the art, and therefore is not describedin detail herein. For other implementations, the PSTN interface 230 maybe omitted, or may be replaced with any other suitable interface thatconnects the GN 200 to a ground-based network (e.g., the Internet).

The LAN interface 240 may provide communication signals to, and receivecommunication signals from, an external LAN. For example, the LANinterface 240 may be coupled to the Internet 108 either directly orthrough additional infrastructure 106, as illustrated in FIG. 1. The LANinterface 240 is well known in the art, and therefore is not describedin detail herein.

The GN interface 245 may provide communication signals to, and receivecommunication signals from, one or more other GNs associated with thesatellite communication system 100 of FIG. 1 (and/or to/from GNsassociated with other satellite communication systems, not shown forsimplicity). For some implementations, the GN interface 245 maycommunicate with other GNs via one or more dedicated communication linesor channels (not shown for simplicity). For other implementations, theGN interface 245 may communicate with other GNs using the PSTN 110and/or other networks such as the Internet 108 (see also FIG. 1). For atleast one implementation, the GN interface 245 may communicate withother GNs via the infrastructure 106.

Overall GN control may be provided by the GN controller 250. The GNcontroller 250 may plan and control utilization of the satellite 300'sresources by the GN 200. For example, the GN controller 250 may analyzetrends, generate traffic plans, allocate satellite resources, monitor(or track) satellite positions, and monitor the performance of the GN200 and/or the satellite 300. The GN controller 250 may also be coupledto a ground-based satellite controller (not shown for simplicity) thatmaintains and monitors orbits of the satellite 300, relays satelliteusage information to the GN 200, tracks the positions of the satellite300, and/or adjusts various channel settings of the satellite 300.

For the example implementation illustrated in FIG. 2, the GN controller250 includes local time, frequency, and position references 251, whichmay provide local time or frequency information to the RF subsystem 210,the digital subsystem 220, and/or the interfaces 230, 240, and 245. Thetime or frequency information may be used to synchronize the variouscomponents of the GN 200 with each other and/or with the satellite(s)300. The local time, frequency, and position references 251 may alsoprovide position information (e.g., ephemeris data) of the satellite(s)300 to the various components of the GN 200. Further, although depictedin FIG. 2 as included within the GN controller 250, for otherimplementations, the local time, frequency, and the position references251 may be a separate subsystem that is coupled to the GN controller 250(and/or to one or more of the digital subsystem 220 and the RF subsystem210).

Although not shown in FIG. 2 for simplicity, the GN controller 250 mayalso be coupled to a network control center (NCC) and/or a satellitecontrol center (SCC). For example, the GN controller 250 may allow theSCC to communicate directly with the satellite(s) 300, for example, toretrieve ephemeris data from the satellite(s) 300. The GN controller 250may also receive processed information (e.g., from the SCC and/or theNCC) that allows the GN controller 250 to properly aim its antennas 205(e.g., at the appropriate satellite(s) 300), to schedule beamtransmissions, to coordinate handoffs, and to perform various otherwell-known functions.

The GN controller 250 may include one or more of a processing circuit232, a memory device 234, or a controller 236 that independently orcooperatively perform operations related to paging, location reporting,connection signaling, and so on for the GN 200 as taught herein. In anexample implementation, the processing circuit 232 is configured (e.g.,programmed) to perform some or all of these operations. In anotherexample implementation, the processing circuit 232 (e.g., in the form ofa processor) executes code stored in the memory device 234 to performsome or all of these operations. In another example implementation, thecontroller 236 is configured (e.g., programmed) to perform some or allof these operations. Although depicted in FIG. 2 as included within theGN controller 250, for other implementations, one or more of theprocessing circuit 232, the memory device 234, or the controller 236 maybe a separate subsystem that is coupled to the GN controller 250 (and/orto one or more of the digital subsystem 220 and the RF subsystem 210).

FIG. 3 is an example block diagram of the satellite 300 for illustrativepurposes only. It will be appreciated that specific satelliteconfigurations can vary significantly and may or may not includeon-board processing. Further, although illustrated as a singlesatellite, two or more satellites using inter-satellite communicationmay provide the functional connection between the GN 200 and the UT 400.It will be appreciated that the disclosure is not limited to anyspecific satellite configuration and any satellite or combinations ofsatellites that can provide the functional connection between the GN 200and UT 400 can be considered within the scope of the disclosure. In oneexample, the satellite 300 is shown to include a forward transponder310, a return transponder 320, an oscillator 330, a controller 340,forward link antennas 351 and 352(1)-352(N), and return link antennas362 and 361(1)-361(N). The forward transponder 310, which may processcommunication signals within a corresponding channel or frequency band,may include a respective one of first bandpass filters 311(1)-311(N), arespective one of first low noise amplifiers (LNAs) 312(1)-312(N), arespective one of frequency converters 313(1)-313(N), a respective oneof second LNAs 314(1)-314(N), a respective one of second bandpassfilters 315(1)-315(N), and a respective one of power amplifiers (PAs)316(1)-316(N). Each of the PAs 316(1)-316(N) is coupled to a respectiveone of antennas 352(1)-352(N), as shown in FIG. 3.

Within each of respective forward paths FP(1)-FP(N), the first bandpassfilter 311 passes signal components having frequencies within thechannel or frequency band of the respective forward path FP, and filterssignal components having frequencies outside the channel or frequencyband of the respective forward path FP. Thus, the pass band of the firstbandpass filter 311 corresponds to the width of the channel associatedwith the respective forward path FP. The first LNA 312 amplifies thereceived communication signals to a level suitable for processing by thefrequency converter 313. The frequency converter 313 converts thefrequency of the communication signals in the respective forward path FP(e.g., to a frequency suitable for transmission from the satellite 300to the UT 400). The second LNA 314 amplifies the frequency-convertedcommunication signals, and the second bandpass filter 315 filters signalcomponents having frequencies outside of the associated channel width.The PA 316 amplifies the filtered signals to a power level suitable fortransmission to the UTs 400 via a respective antenna 352. The returntransponder 320, which includes a number N of return paths RP(1)-RP(N),receives communication signals from the UT 400 along the return servicelink 302R via the antennas 361(1)-361(N), and transmits communicationsignals to the GN 200 along the return feeder link 301R via one or moreof the antennas 362. Each of the return paths RP(1)-RP(N), which mayprocess communication signals within a corresponding channel orfrequency band, may be coupled to a respective one of the antennas361(1)-361(N), and may include a respective one of first bandpassfilters 321(1)-321(N), a respective one of first LNAs 322(1)-322(N), arespective one of frequency converters 323(1)-323(N), a respective oneof second LNAs 324(1)-324(N), and a respective one of second bandpassfilters 325(1)-325(N).

Within each of the respective return paths RP(1)-RP(N), the firstbandpass filter 321 passes signal components having frequencies withinthe channel or frequency band of the respective return path RP, andfilters signal components having frequencies outside the channel orfrequency band of the respective return path RP. Thus, the pass band ofthe first bandpass filter 321 may for some implementations correspond tothe width of the channel associated with the respective return path RP.The first LNA 322 amplifies all the received communication signals to alevel suitable for processing by the frequency converter 323. Thefrequency converter 323 converts the frequency of the communicationsignals in the respective return path RP (e.g., to a frequency suitablefor transmission from the satellite 300 to the GN 200). The second LNA324 amplifies the frequency-converted communication signals, and thesecond bandpass filter 325 filters signal components having frequenciesoutside of the associated channel width. Signals from the return pathsRP(1)-RP(N) are combined and provided to the one or more antennas 362via a PA 326. The PA 326 amplifies the combined signals for transmissionto the GN 200.

The oscillator 330, which may be any suitable circuit or device thatgenerates an oscillating signal, provides a forward local oscillatorsignal LO(F) to the frequency converters 313(1)-313(N) of the forwardtransponder 310, and provides a return local oscillator signal LO(R) tothe frequency converters 323(1)-323(N) of the return transponder 320.For example, the LO(F) signal may be used by the frequency converters313(1)-313(N) to convert communication signals from a frequency bandassociated with the transmission of signals from the GN 200 to thesatellite 300 to a frequency band associated with the transmission ofsignals from the satellite 300 to the UT 400. The LO(R) signal may beused by the frequency converters 323(1)-323(N) to convert communicationsignals from a frequency band associated with the transmission ofsignals from the UT 400 to the satellite 300 to a frequency bandassociated with the transmission of signals from the satellite 300 tothe GN 200.

The controller 340, which is coupled to the forward transponder 310, thereturn transponder 320, and the oscillator 330, may control variousoperations of the satellite 300 including (but not limited to) channelallocations. In one aspect, the controller 340 may include a processingcircuit 364 (e.g., a processor) coupled to a memory (e.g., a memorydevice 366). The memory may include a non-transitory computer-readablemedium (e.g., one or more nonvolatile memory elements, such as an EPROM,an EEPROM, a Flash memory, a hard drive, etc.) storing instructionsthat, when executed by the processing circuit 364, cause the satellite300 to perform operations including (but not limited to) those describedherein.

FIG. 4 is an example block diagram of the UT 400 or the UT 401 forillustrative purposes only. It will be appreciated that specific UTconfigurations can vary significantly. Thus, the disclosure is notlimited to any specific UT configuration and any UT that can provide thefunctional connection between the satellite 300 and the UE 500 or 501can be considered within the scope of the disclosure.

UTs may be used in various applications. In some scenarios, a UT mayprovide a cellular backhaul. In this case, the UT may have a relativelylarge antenna and/or multiple antennas (e.g., to protect againstblockage). In some scenarios, a UT may be deployed in an enterpriseenvironment (e.g., placed on the roof of a building). In this case, theUT may have a relatively large antenna and/or multiple antennas (e.g.,to provide relatively high backhaul bandwidth). In some scenarios, a UTmay be deployed in a residential environment (e.g., placed on the roofof a house). In this case, the UT may have a smaller (and relativelyinexpensive) antenna and provide fixed access for data service (e.g.,Internet access). In some scenarios, a UT may be deployed in a maritimeenvironment (e.g., placed on a cruise ship, a cargo ship, etc.). In thiscase, the UT may have a relatively large antenna and/or multipleantennas (e.g., to prevent blockage and provide relatively highbandwidth data service). In some scenarios, a UT may be deployed on avehicle (e.g., carried by first responders, emergency crews, etc.). Inthis case, the UT may have a smaller antenna and used to providetemporary Internet access to a particular area (e.g., where cellularservice is out). Other scenarios are possible.

The configuration of a particular UT may depend on the application forwhich the UT will be used. For example, the type of antenna, the antennashape, the quantity of antennas, the supported bandwidth, the supportedtransmit power, the receiver sensitivity, etc., may depend on thecorresponding application. As one example, a flat panel antenna (with arelatively low profile) may be used for aircraft applications.

In the example of FIG. 4, the UT is shown to include a transceiver whereat least one antenna 410 is provided for receiving forward linkcommunication signals (e.g., from the satellite 300), which aretransferred to an analog receiver 414, where they are down-converted,amplified, and digitized. A duplexer element 412 is often used to allowthe same antenna to serve both transmit and receive functions.Alternatively, a UT transceiver may employ separate antennas foroperating at different transmit and receive frequencies.

The digital communication signals output by the analog receiver 414 aretransferred to at least one digital data receiver 416A and at least onesearcher receiver 418. Additional digital data receivers (e.g., asrepresented by a digital data receiver 416N) can be used to obtaindesired levels of signal diversity, depending on the acceptable level oftransceiver complexity, as would be apparent to one skilled in therelevant art.

At least one user terminal control processor 420 is coupled to thedigital data receivers 416A-416N and the searcher receiver 418. Thecontrol processor 420 provides, among other functions, basic signalprocessing, timing, power and handoff control or coordination, andselection of frequency used for signal carriers. Another basic controlfunction that may be performed by the control processor 420 is theselection or manipulation of functions to be used for processing varioussignal waveforms. Signal processing by the control processor 420 caninclude a determination of relative signal strength and computation ofvarious related signal parameters. Such computations of signalparameters, such as timing and frequency may include the use ofadditional or separate dedicated circuitry to provide increasedefficiency or speed in measurements or improved allocation of controlprocessing resources.

The outputs of the digital data receivers 416A-416N are coupled todigital baseband circuitry 422 within the UT 400. The digital basebandcircuitry 422 includes processing and presentation elements used totransfer information to and from the UE 500 as shown in FIG. 1, forexample. Referring to FIG. 4, if diversity signal processing isemployed, the digital baseband circuitry 422 may include a diversitycombiner and decoder (not shown). Some of these elements may alsooperate under the control of, or in communication with, a controlprocessor 420.

When voice or other data is prepared as an output message or acommunication signal originating with the UT 400, the digital basebandcircuitry 422 is used to receive, store, process, and otherwise preparethe desired data for transmission. The digital baseband circuitry 422provides this data to a transmit modulator 426 operating under thecontrol of the control processor 420. The output of the transmitmodulator 426 is transferred to a power controller 428 which providesoutput power control to a transmit power amplifier 430 for finaltransmission of the output signal from the antenna 410 to a satellite(e.g., the satellite 300).

In FIG. 4, the UT transceiver also includes a memory 432 associated withthe control processor 420. The memory 432 may include instructions forexecution by the control processor 420 as well as data for processing bythe control processor 420. In the example illustrated in FIG. 4, thememory 432 may include instructions for performing time or frequencyadjustments to be applied to an RF signal to be transmitted by the UT400 via the return service link to the satellite 300.

In the example illustrated in FIG. 4, the UT 400 also includes optionallocal time, frequency and/or position references 434 (e.g., a GPSreceiver), which may provide local time, frequency and/or positioninformation to the control processor 420 for various applications,including, for example, time or frequency synchronization for the UT400.

The digital data receivers 416A-416N and the searcher receiver 418 areconfigured with signal correlation elements to demodulate and trackspecific signals. The searcher receiver 418 is used to search for pilotsignals, or other relatively fixed pattern strong signals, while thedigital data receivers 416A-416N are used to demodulate other signalsassociated with detected pilot signals. However, a digital data receiver416 can be assigned to track the pilot signal after acquisition toaccurately determine the ratio of signal chip energies to signal noise,and to formulate pilot signal strength. Therefore, the outputs of theseunits can be monitored to determine the energy in, or frequency of, thepilot signal or other signals. These receivers also employ frequencypaging elements that can be monitored to provide current frequency andtiming information to the control processor 420 for signals beingdemodulated.

The control processor 420 may use such information to determine to whatextent the received signals are offset from the oscillator frequency,when scaled to the same frequency band, as appropriate. This and otherinformation related to frequency errors and frequency shifts can bestored in a storage or memory element (e.g., the memory 432) as desired.

The control processor 420 may also be coupled to the UE interfacecircuitry 450 to allow communication between the UT 400 and one or moreUEs. The UE interface circuitry 450 may be configured as desired forcommunication with various UE configurations and accordingly may includevarious transceivers and related components depending on the variouscommunication technologies employed to communicate with the various UEssupported. For example, the UE interface circuitry 450 may include oneor more antennas, a wide area network (WAN) transceiver, a wirelesslocal area network (WLAN) transceiver, a Local Area Network (LAN)interface, a Public Switched Telephone Network (PSTN) interface and/orother known communication technologies configured to communicate withone or more UEs in communication with the UT 400.

The control processor 420 may include one or more of a processingcircuit 442, a memory device 444, or a controller 446 that independentlyor cooperatively perform operations related to paging, locationreporting, connection signaling, and so on for the UT 400 as taughtherein. In an example implementation, the processing circuit 442 isconfigured (e.g., programmed) to perform some or all of theseoperations. In another example implementation, the processing circuit442 (e.g., in the form of a processor) executes code stored in thememory device 444 to perform some or all of these operations. In anotherexample implementation, the controller 446 is configured (e.g.,programmed) to perform some or all of these operations. Althoughdepicted in FIG. 4 as included within the control processor 420, forother implementations, one or more of the processing circuit 442, thememory device 444, or the controller 446 may be a separate subsystemthat is coupled to the control processor 420.

FIG. 5 is a block diagram illustrating an example of the UE 500, whichalso can apply to the UE 501 of FIG. 1. The UE 500 as shown in FIG. 5may be a mobile device, a handheld computer, a tablet, a wearabledevice, a smart watch, or any type of device capable of interacting witha user, for example. Additionally, the UE 500 may be a network sidedevice that provides connectivity to various ultimate end user devicesand/or to various public or private networks. In the example shown inFIG. 5, the UE 500 may include a LAN interface 502, one or more antennas504, a wide area network (WAN) transceiver 506, a wireless local areanetwork (WLAN) transceiver 508, and a satellite positioning system (SPS)receiver 510. The SPS receiver 510 may be compatible with the GlobalPositioning System (GPS), the Global Navigation Satellite System(GLONASS) and/or any other global or regional satellite basedpositioning system. In an alternate aspect, the UE 500 may include aWLAN transceiver 508, such as a Wi-Fi transceiver, with or without theLAN interface 502, the WAN transceiver 506, and/or the SPS receiver 510,for example. Further, the UE 500 may include additional transceiverssuch as Bluetooth, ZigBee and other known technologies, with or withoutthe LAN interface 502, the WAN transceiver 506, the WLAN transceiver 508and/or the SPS receiver 510. Accordingly, the elements illustrated forthe UE 500 are provided merely as an example configuration and are notintended to limit the configuration of UEs in accordance with thevarious aspects disclosed herein.

In the example shown in FIG. 5, a processor 512 is connected to the LANinterface 502, the WAN transceiver 506, the WLAN transceiver 508 and theSPS receiver 510. Optionally, a motion sensor 514 and other sensors mayalso be coupled to the processor 512.

A memory 516 is connected to the processor 512. In one aspect, thememory 516 may include data 518 which may be transmitted to and/orreceived from the UT 400, as shown in FIG. 1. Referring to FIG. 5, thememory 516 may also include stored instructions 520 to be executed bythe processor 512 to perform the process steps for communicating withthe UT 400, for example. Furthermore, the UE 500 may also include a userinterface 522, which may include hardware and software for interfacinginputs or outputs of the processor 512 with the user through light,sound or tactile inputs or outputs, for example. In the example shown inFIG. 5, the UE 500 includes a microphone/speaker 524, a keypad 526, anda display 528 connected to the user interface 522. Alternatively, theuser's tactile input or output may be integrated with the display 528 byusing a touch-screen display, for example. Once again, the elementsillustrated in FIG. 5 are not intended to limit the configuration of theUEs disclosed herein and it will be appreciated that the elementsincluded in the UE 500 will vary based on the end use of the device andthe design choices of the system engineers.

Additionally, the UE 500 may be a user device such as a mobile device orexternal network side device in communication with but separate from theUT 400 as illustrated in FIG. 1, for example. Alternatively, the UE 500and the UT 400 may be integral parts of a single physical device.

In the example shown in FIG. 1, the two UTs 400 and 401 may conducttwo-way communication with the satellite 300 via return and forwardservice links within a beam coverage. A satellite may communicate withmore than two UTs within a beam coverage. The return service link fromthe UTs 400 and 401 to the satellite 300 may thus be a many-to-onechannel. Some of the UTs may be mobile while others may be stationary,for example. In a satellite communication system such as the exampleillustrated in FIG. 1, multiple UTs 400 and 401 within a beam coveragemay be time-division-multiplexed (TDM′ed),frequency-division-multiplexed (FDM′ed), or both.

At some point in time, a UT may need to be handed-off to anothersatellite (not shown in FIG. 1). Handoff may be caused by scheduledevents or unscheduled events.

Several examples of handoff due to scheduled events follow. Inter-beamand inter-satellite handoff may be caused by movement of the satellite,movement of the UT, or a satellite beam being turned off (e.g., due to aGeo-stationary satellite (GEO) restriction). Handoff also may be due toa satellite moving out of the GN's range while the satellite is stillwithin the UT's line of sight.

Several examples of handoff due to nonscheduled events follow. Handoffmay be triggered by a satellite being obscured by an obstacle (e.g., atree). Handoff also may be triggered due to a drop in channel quality(e.g., signal quality) due to rain fade or other atmospheric conditions.

In some implementations, at a particular point in time, a particularsatellite may be controlled by a particular entity (e.g., a networkaccess controller, NAC) in an GN. Thus, an GN may have several NACs(e.g., implemented by the GN controller 250 of FIG. 2), each of whichcontrols a corresponding one of the satellites controlled by the GN. Inaddition, a given satellite may support multiple beams Thus, over time,different types of handoff may occur.

In inter-beam handoff, a UT is handed-off from one beam of a satelliteto another beam of the satellite. For example, the particular beamserving a stationary UT may change over time as the serving satellitemoves.

In inter-satellite handoff, a UT is handed-off from the current servingsatellite (referred to as the source satellite) to another satellite(referred to as the target satellite). For example, a UT may behanded-off to the target satellite as the source satellite moves awayfrom the UT and the target satellite moves toward the UT.

II. Example Details of a Satellite Communication System

FIG. 6 illustrates a non-geosynchronous satellite communication system600, such as a LEO satellite communication system for data, voice,video, or other communication, in which the above information,signaling, and procedures may be used. The communication system 600includes UT 602 that can communicate with a GN 604 via a satellite 606.The UT 602, the GN 604, and the satellite 606 may respectivelycorrespond to, for example, the UT 400, the GN 200, and the satellite300 of FIG. 1.

The GN 604 also includes a core network control plane (CNCP) 616 and acore network user plane (CNUP) 618, or other similar functionality, forcommunicating with another network 620. In some aspects, a CNCP mayprovide mobility management functionality such as, for example, keepingtrack of the current location of UTs through the use of paging areas,location areas, routing areas, or some other suitable technique;controlling paging for UTs; and providing access control for UTs. Insome aspects, a CNUP may provide gateway functionality such as, forexample, interfacing with a packet network and/or other types ofnetworks. The network 620 may thus represent, for example, a corenetwork (e.g., 3G, 4G, 5G, etc.), an intranet, the Internet, some othertype of network, or a combination thereof.

The GN 604 includes network access controllers (NACs) 612, each of whichinterfaces with one or more radio frequency (RF) subsystems 614 forcommunicating with the UT 602 and other UTs (not shown) via thesatellite 606 (or some other satellite, not shown). In some aspects, aNAC 612 may provide radio interface functionality such as modulation,demodulation, channel coding, channel decoding, multiplexing anddemultiplexing. In addition, a NAC 612 may support Radio functions suchas broadcast of system information and Radio connection control.

Example functionality of a NAC (e.g., a NAC 612 of FIG. 6) will bedescribed in more detail in the context of a satellite communicationsystem 700 of FIG. 7. As shown, a NAC may include two components, a BxPand an AxP, for controlling and/or communicating via a satellite. Thus,in general, the functionality of the components of FIG. 7 are similar tothe functionality of the components of the satellite communicationsystem 600 of FIG. 6.

In some aspects, a BxP corresponds to beam-related functionality. Forexample, the term BxP may refer to a combination of a Beam ControlProcessor (BCP) and a Beam Traffic Processor (BTP). That is, the acronymBxP may stand for Beam Control/Traffic Processor. In some aspects, a BxPmay include radio network components for controlling a satellite. Forexample, a BxP may include, for a given cell/beam of a satellite, acorresponding set of digital circuits that serves that cell/beam. Thus,in some aspects, a BxP corresponds to a particular antenna. Also, insome aspects, a given BxP may be associated with a particular band for agiven cell/beam of a satellite. In some scenarios, a logical BxP may beuniquely identified by a 4-tuple including a satellite access network(SAN), a GN antenna, a Satellite Beam, and a forward service link (FSL)Frequency.

In some aspects, an AxP corresponds to an anchor point. For example, theterm AxP may refer to a combination of an Anchor Control Processor (ACP)and an Anchor Traffic Processor (ATP). That is, the acronym AxP maystand for Anchor Control/Traffic Processor. In some aspects, an anchorpoint may be associated with a particular region (e.g., anadministrative region, a country boundary, etc.). A given AxP may serveone or more satellites. Also, a given satellite may service one or moreAxPs.

Referring to FIG. 7, at a given point in time, a UT 702 communicateswith one of the AxPs (e.g., the AxP 704A) via a satellite 706 and one ofthe BxPs (e.g., a BxP 708A), where each BxP includes or is associatedwith a satellite RF subsystem (e.g., a subsystem 710A).

In the above scenario, a UT in connected mode may undergo two types ofhandoff: BxP handoff or AxP handoff. For example, as satellites move ina non-GSO satellite system, the cells/beams (and, hence, the circuitsand antennas associated with those cells/beams) used to serve a given UTwill change over time. Thus, in some aspects, a BxP handoff maycorrespond to a handoff to a different cell/beam (or antenna, etc.). Asanother example, rain fade on a particular cell/beam operating on afirst band may necessitate a switch to a different band for thatcell/beam. Thus, in some aspects, a BxP handoff may correspond to ahandoff to a different band for a given cell/beam. An AxP handoffcorresponds to handoff to a different anchor point. For example, a UTmay move to a different administrative region (AR), therebynecessitating a change in the serving AxP. A BxP handoff might or mightnot be associated with an AxP handoff.

III. Paging, Location, and Forbidden Area Procedures and ConnectionSignaling

The disclosure relates in some aspects to providing paging area (PA)information to a user terminal (UT), communicating UL locationinformation, handing forbidden areas, and associated connectionsignaling. To this end, a GN and/or a UT may perform paging-relatedoperations, location-related operations, connection-related operations.For example, referring again to FIG. 6, the GN 604 may maintain pagingarea information 622 and location information 624, and the UT 602 maymaintain paging area information 626 and location information 628. Inaddition, the UT 602 and the GN 604 may generate, control, send, andreceive paging area information 630, location information 632, andconnection signaling 634 exchanged via messages relayed by the satellite606.

These paging-related operations may relate in some aspects to defining areserved value for a Paging Area Code (PAC) that a UT can use if the UThas not yet been assigned a PAC. The reserved PAC is known to the UT andan associated Anchor Control/Traffic Processor (AxP), but might not beused over-the-air. For example, control plane procedures of the UT mayuse the reserved PAC when invoking signaling operations.

The paging-related operations may also relate in some aspects toproviding PAC information to a UT. In some aspects, an ACP may send aRadio Connection Reconfiguration message (including a new PAC, and anindication of when to apply the change) to a UT to pass PAC informationto the UT. A corresponding Radio Connection Release message may includea Duration parameter and a Restricted Area Definition. In some aspects,a network may send a special PAC to a UT is the UT is in or near aforbidden area.

The connection-related operations may relate in some aspects tosignaling for communicating new PACs and old PACS. For example, a RadioConnection Reject message (e.g., including a wait time value, and a PAC)may be sent to assign a new PAC for a UT (e.g., for a first PACassignment, a PAC re-assignment due to load balancing, or some othertype of PAC assignment). As another example, a Radio Connection Rejectmessage (e.g., including a wait time value, a new PAC, a flag thatrequests sending of old PAC information in a connection request) may besent to assign a new PAC for a UT. A UT may send a Radio ConnectionRequest message (e.g., including old PAC for the UT) when the UTrequests a connection with a new PAC.

The connection-related operations may relate in some aspects toconnection release signaling. For example, a Location Indication (e.g.,including a flag requesting release of a connection) may be sent torelease a Core Network Interface (CNI) connection and/or a RadioConnection when a UT is done sending location information and is goingto go back to idle mode. As another example, a UT may send a RadioConnection Release Request to an Anchor Control/Traffic Processor (AxP)to release a CNI connection and/or a Radio Connection when a UT is donesending location information, when a UT is done downloading a satellitetransition table, or in response to a trigger based on any otheruse-case, and where the UT wants to go back to idle mode.

The location-related operations may relate in some aspects to locationreporting. For example, a gateway may send a Radio ConnectionReconfiguration message (e.g., including location thresholds for idlemode and/or connected mode) to a UT. This message may be used for finetuning UT Location Reporting in border areas near forbidden regions. Asanother example, an AxP may send a Location Request message to a UT torequest the UT's latest location (e.g., GPS location).

The above operations may relate in some aspects to forcing a UT toinvoke an update procedure. For example, the network may send to the UTa Radio Connection Release message that includes information such as: aduration indication, a Restricted Area definition, an indication toForce Initiation of a Core Network Control Layer (CNCL) updateprocedure, or any combination thereof. A UT may start an updateprocedure using an invalid value for the PAC. The ACP replaces theinvalid PAC value with a forbidden PAC value that is then sent to theCore Network Control Plane (CNCP). In response, the CNCP performs areject update procedure.

These and other aspects of the disclosure will be treated in more detailin conjunction with FIGS. 8-30 that follow. For purposes of explanation,these details will be described in the context of a satellite systemthat includes one or more of CNCPs, AxPs, and BxPs, among othercomponents and uses paging areas and other relates constructs. It shouldbe appreciated, however, that the teachings herein may be applicable toother types of systems, other types of components, and other constructs.

IV. Paging Details

A satellite system may use Administrative Regions (ARs) to identifygeographic areas that require specific business or legal treatment ofthe UTs, such as differentiated pricing or different legal rules. TheARs may be aligned with country boundaries. In some cases, the ARs mightnot be communicated to UTs. For example, ARs could exist only as part ofnetwork planning and may be available to the GN nodes. Each AR maycontain multiple Paging Areas (PAs).

Each PA may be identified by a Paging Area Code (PAC). A UT may movewithin an AR freely without needing to update its PAC. The core networkand charging infrastructure may maintain a mapping of which PAC maps towhich Administrative Region.

The PA might not provide any further refinement of geographic locationthan what is provided by the AR. That means there might not be a fixedmapping between a PA and a Cell ID (e.g., to a geographical area) and acell might not broadcast any specific PAC in its Broadcast InformationBlocks (BIBs).

From the core network perspective, a PAC may uniquely identify an AnchorControl Processor (ACP). A Core Network Control Plane (CNCP) may use thelast PAC reported by the UT to identify the ACP to deliver a page forthe UT. The ACP may use the location of the UT to refine the satellitesand the beams that may be used to page the UT.

In some aspects, the network may change the PAC for a UT under one ormore conditions. In a first example condition, when a UT moves betweenARs, the UT may be provided a new PAC that belongs to the new AR. In asecond example condition, when the network decides to serve a UT from adifferent ACP, the UT may be provided a new PAC that belongs to the newACP. PAC reallocation may be done for various reasons. For example, theACP might not be able to serve the UT due to backhaul congestion, theremay be load balancing across ACPs, or there may be hardware and/orsoftware failures. These examples are indicative and not exhaustive. Ina third example condition, when the network decides to deny service to aUT based on its geographic (GPS or some other positioning system)location, the network may use forbidden Paging Area (PA) procedures andassign PACs which are forbidden. The core network has awareness offorbidden PAs. The network changing the PAC for a UT may, in turn,trigger a Paging Area Update (PAU) procedure initiated by the UT.

In some aspects, a satellite system may map a geographic area based onthe country, the AR, the PA, the Cell/Beam, or any combination thereof.A country may include one AR or multiple ARs. In some cases, a single ARmay cover multiple countries. An AR may contain multiple Paging Areas. APaging Area might not specify any well-defined geographic area. ACell/Beam may cover a relatively large geographic area and may cover,for example, part of an AR, one AR, multiple ARs, or any combination ofthereof.

In a satellite system, a cell/beam may cover a relatively largegeographic area including both a service area and a forbidden area(e.g., an area where a given UT is not authorized to receive service) atthe same time. Moreover, a satellite system may use the precise location(e.g., the GPS location) of the UT to identify the cell/beam in which topage the UT. Hence, it may be desirable to base a serviceavailability/denial decision on a GPS location of the UT as opposed to,for example, a Cell ID or a PA ID.

A satellite system may use PA IDs to identify Anchor Nodes (ACPs) in theGN that handle the radio connection for a specific UT. Here, a PAC maybe assigned to a UT via a unicast messages (e.g., via a connectionreject) as opposed to via a broadcast of system information.

IV-A. Example Issues

The disclosure relates in some aspects to the use of Radio ConnectionLayer (RCL) protocols and Core Network Control Layer (CNCL) protocolsfor connection management between a UT and a CNCP. Several issuesassociated with mobility may arise with respect to the use of these orother protocols in a satellite system.

A first example issue (also referred to as Issue #1) is that SystemInformation of a cell (e.g., sent in a BIB such as BIB1) might notcontain paging area information. For example, PAC information might notbe available after camping. Since CNCL mobility procedures may be basedon the PA, a CNCL protocol might not work in this case.

A second example issue (also referred to as Issue #2) involves PACrelocation due to a change in the serving ACP. For example, a CNCLprocedure might not expect a change of PAC except for idle modeselection/reselection or connected mode handoff. Thus, one should ensurethat a change of a PAC during an ongoing data/signaling procedure willbe handled effectively. For example, a new PAC assignment may be madeduring a Radio signaling establishment procedure.

A third example issue (also referred to as Issue #3) is that PACinformation might not give any information about geographic area.However, precise UT GPS location may be desirable to provide/denyservice to a UT.

A fourth example issue (also referred to as Issue #4) is that a UT maybe expected to report its GPS location to the ACP whenever the UT movesbeyond a significant distance (e.g., defined by the network) from theUT's last reported location. However, UTs in IDLE mode might not have asignaling connection with the ACP to send location information. The UTand the ACP might not be able to establish a secured radio connectionand data bearers on their own when there is no actual user data. Forexample, they may need the network to provide relevant keys to secure aradio connection. Also, the air interface might not support efficientconnection management.

A fifth example issue (also referred to as Issue #5) is that there is noprovision to reconfigure a location reporting threshold during connectedmode.

A sixth example issue (also referred to as Issue #6) is that there is noprovision to request a UT's latest location.

IV-B. Example Design Options

Several design options that may address these and other issues arepresented herein. Each design option is described in conjunction with atleast one corresponding message flow diagram. FIGS. 8-14 describeseveral of these design options at a relatively high level. FIGS. 15A-30describe several of these design options using more detailed examples.

Symbolic values for some signaling parameters may be used in the messageflow diagrams for clarity. For example, a “default PAC” parameter(PACdefault) may represent a value reserved (e.g., for UT internal usein some cases) from the valid range of PACs. The ACP does not assignthis reserved value to any specific UTs (e.g., the default PAC does notcorrespond to a particular PA). Parameters such as PACa/PACb mayrepresent a value from the valid range of PACs that the ACP treats asallowed. A “forbidden PAC” parameter (PACf) may represent a value fromthe valid range of PACs that the ACP treats as forbidden. An “invalidPAC” parameter (PACinv) may represent a value outside the valid range ofPACs. A Forbidden PA Set may be defined and provisioned between the ACPand the CNCP. New Information Fields (IFs) added to the air interfacemay be indicated in the message diagrams. In addition, behavioralimpacts on the UT, a Beam Control/Traffic Processor (BxP), or an AnchorControl/Traffic Processor (AxP) may be indicated in the messagediagrams.

V. High Level Examples

FIGS. 8-14 describe example processes for management of paging,forbidden areas, connection signaling, and location reporting inaccordance with the teachings herein. Each of these figures describesoperations at a first device (e.g., a UT), operations at a second device(e.g., a GN), and signaling between the first and second device.

FIG. 8 illustrates a process 800 that involves using a default PAC toobtain a new PAC. In some aspects, the process 800 may address Issue #1discussed above. At block 802, the first device determines that is notcurrent assigned a valid PAC. For example, the first device might nothave attached to a network after powering on. At block 804, at somepoint in time, the first device camps on a cell. At block 806, the firstdevice uses a default PAC (e.g., a special PAC that is dedicated forthis purpose) to initiate a mobility procedure (e.g., a CNCL mobilityprocedure). To this end, the first device sends a connection request 808that includes the default PAC to the second device. At block 810, uponreceiving the connection request 808, the second device assigns a validPAC to the first device. Thus, at block 812, the second device sends anew PAC (“new” from the perspective of the first device) to the firstdevice. To this end, the second device sends a connection reject 814that includes the new PAC to the first device. In some scenarios, thenew PAC may be sent with a request for the first device to “immediately”(e.g., without waiting for some other connection trigger) attempt toreconnect to the network. The first device receives the connectionreject 814 with the new PAC at block 816. At block 818, the first deviceuses the new PAC to establish a connection. For example, the firstdevice may send a connection request 820 that includes the new PAC tothe second device. This connection establishment process may beperformed “immediately” if the new PAC was sent with a request toimmediately attempt to reconnection. Upon receiving the connectionrequest 820 at block 822, the second device may establish a connectionwith the first device.

FIG. 9 illustrates a process 900 that involves reassigning a PAC. Insome aspects, the process 900 may address Issue #2 discussed above. Atblock 902, at some point in time, the first device uses its currentlyassigned PAC to establish a connection with a network. To this end, thefirst device sends a connection request 904 that includes the PAC to thesecond device. The second device receives the connection request 904 atblock 906. At block 908, the second device assigns a new PAC to thefirst device (e.g., due to a handoff of the UT to a different AxP orsome other event). At block 910, the second device sends this new PAC tothe first device. To this end, the second device sends a connectionreject 912 that includes the new PAC. In some scenarios, the new PAC maybe sent with a request for the first device to “immediately” attempt toreconnect to the network. Alternatively, or in addition, the new PAC maybe sent with a request for the first device to send its old PAC (e.g.,the PAC that the first device previously used at block 902) whenrequesting a connection. The first device receives the connection rejectat block 914. At block 916, the first device uses the new PAC to requesta connection. For example, the first device may send a connectionrequest 918 that includes the new PAC to the second device. Theconnection request 918 may include the first device's old PAC if theconnection reject 912 included a request for the old PAC. The seconddevice receives the connection request 918 at block 906. At block 922,the second device may determine the location of the first device basedon the old PAC. At block 924, the second device may establish aconnection with the first device.

FIG. 10 illustrates a process 1000 that involves forbidden areamanagement (e.g., a device enters a forbidden area). In some aspects,the process 1000 may address Issue #3 discussed above. At block 1002,the first device reports its current location. For example, the firstdevice may send a location indication 1004 to the second device. Thesecond device receives the location indication 1004 at block 1006. Atblock 1008, the second device may determine that the reported locationis in a forbidden area. As a result, at block 1010, the second devicereconfigures the first device with a PAC associated with a forbiddenarea (designated PACO. For example, the second device may send aconnection reconfiguration 1012 that includes PACf to the second device.The first device receives the connection reconfiguration 1012 with thePACf at block 1014. At block 1016 the second device sends informationabout the area of the forbidden area to the first device. In somescenarios, this information may include an ellipsoid point (e.g., acenter point) and a distance from the ellipsoid point (e.g., a radius)of the forbidden area. In the example of FIG. 10, the second devicesends a connection release 1018 that includes the forbidden areainformation. The connection release 1018 may also include a request tothe first device to update its configuration upon release. The firstdevice receives the connection release 1018 with the forbidden areainformation at block 1020. In response, the first device starts one ormore service restriction counters at block 1022. For example, the firstdevice may be configured to wait for a designated period of time beforeattempting to reconnect. At block 1024, the first device uses the PACfto request a connection. For example, the first device may send aconnection request 1026 that includes the PACf to the second device. Asa result of receiving the connection request 1026 with the PACf at block1028, the second device rejects the paging area update. As discussedbelow, the first device may then add PACf to its list of forbidden PACs.

FIG. 11 illustrates a process 1100 that involves forbidden areamanagement (e.g., a device leaves a forbidden area). In some aspects,the process 1100 may address Issue #3 discussed above. At block 1102,the first device determines that a service restriction no longerapplies. For example, the first device may determine, based on theforbidden area information, that it is no longer in a forbidden area. Atblock 1104, the first device uses the default PAC to request aconnection. For example, the first device may send a connection request1106 that includes the default PAC to the second device. The seconddevice receives the connection request 1106 with the default PAC atblock 1108. At block 1110, the second device assigns a valid PAC to thefirst device. Thus, at block 1112, the second device sends a new PAC tothe first device. For example, the second device may send a connectionreject 1114 that includes the new PAC to the first device. In somescenarios, the new PAC may be sent with a request for the first deviceto “immediately” (e.g., without waiting for some other connectiontrigger) attempt to reconnect to the network. The first device receivesthe connection reject 1114 with the new PAC at block 1116. At block1118, the first device uses the new PAC to request a connection. Forexample, the first device may send a connection request 820 thatincludes the new PAC to the second device. This connection establishmentprocess may be performed “immediately” if the new PAC was sent with arequest to immediately attempt to reconnection. Upon receiving theconnection request 1120 at block 1122, the second device may establish aconnection with the first device upon determining that the first deviceis not in the forbidden area. The second device may make thisdetermination, for example, based on the location of the first device asmaintained in a database or as received in a location indication fromthe first device.

FIG. 12 illustrates a process 1200 that involves an efficient connectionrelease procedure (e.g., a UT sends location information with a releaserequest). In some aspects, the process 1200 may address Issue #4discussed above. At block 1202, the first device and the second deviceestablish a connection for a particular procedure. At block 1204, thefirst device sends a location indication 1206 that includes a request torelease the connection once the procedure ends to the second device. Forexample, the location indication 1206 may include a connection releaseindication that is set to a value of TRUE. The second device receivesthe location indication 1206 at block 1208. At block 1210, the procedureof block 1202 ends. In response, and as a result of receiving theconnection release indication, the second device immediately releasesthe context for the connection at block 1212. At block 1214, the seconddevice sends a connection release 1216 to the first device. The firstdevice thus receives the connection release 1216 at block 1218.

FIG. 13 illustrates a process 1300 that involves efficient connectionrelease procedures (e.g., a UT sends a request for immediate release).In some aspects, the process 1300 may address Issue #4 discussed above.At block 1302, the first device and the second device establish aconnection for a particular procedure. At block 1304, the first devicesends a location indication 1306 to the second device. The second devicereceives the location indication 1306 at block 1308. At block 1310, thefirst device determines that the procedure of block 1302 ends. Inresponse, the first device requests that the connection be release atblock 1312. For example, the first device may send a connection releaserequest 1314 to the second device. As a result of receiving theconnection release request 1314, the second device immediately releasesthe context for the connection at block 1316. At block 1318, the seconddevice sends a connection release 1320 to the first device. The firstdevice thereby receives the connection release 1320 at block 1322.

FIG. 14 illustrates a process 1400 that involves requesting UT locationinformation and reconfiguring a location reporting threshold. In someaspects, the process 1400 may address Issues #5 and #6 discussed above.At block 1402, in some scenarios, the second device may request that thefirst device report its location. For example, the second device maysend a location request 1404 to the first device. Either in response tothe location request 1404 or based on some other trigger (e.g., atrigger based on a location reporting threshold), the first devicedetermines its location at block 1406. At block 1408, the first devicesends a location indication 1410 to the second device. At block 1412,the second device stores the location information for the first devicein a database. At block 1414, the second device determines that thelocation of the first device is near or approaching a forbidden area. Asa result of this determination, at block 1416, the second device updatesone or more location reporting thresholds for the first device. At block1418, the second device sends the updated location reportingthreshold(s) to the first device. For example, the second device maysend a connection reconfiguration 1420 that includes the updatedlocation reporting threshold(s). The first device receives theconnection reconfiguration 1420 at block 1422. At block 1424, the firstdevice uses the updated location reporting threshold(s) to determinewhen to report the first device's location.

VI. Detailed Example for Default PAC

The disclosure relates in some aspects to defining a reserved value fora Paging Area Code (herein referred to as PACdefault) to be used, forexample, in cases where a UT does not yet have a network assigned PAC.In some aspects, PACdefault may be used to address Issue #1 discussedabove (no PA information in Broadcast Information B lock).

A PACdefault may be known to a UT and an ACP, and used internallybetween a Radio Connection Layer (RCL) and a Core Network Control Layer(CNCL) within the UT. In addition, the ACP might not assign this specialPAC value to any specific UT. Once a UT is camped on a cell, if no priorPAC information is available to the UT, the UT may use PACdefault forthe UT's Core Network Control Layer (CNCL) procedures until a new PAC isassigned by the ACP.

A PACdefault may or may not be sent over the air. For example, in someimplementations, a UT may send a PACdefault in a Radio ConnectionRequest message over the air (e.g., after an initial attach to anetwork). For example, the UT may send a PACdefault to the ACP totrigger allocation of a valid PAC as discussed below. In otherimplementations, a UT may simply use the PACdefault value internallysuch that the UT/ACP do not send PACdefault in any signaling messageover the air.

Once a UT has camped on a cell, and if no prior PAC information isavailable in the UT, the UT may use PACdefault for all of its NASprocedures. For example, a Radio Connection may be requested usingPACdefault. An ACP will then assigns a new PAC for the UT and rejectsthe Radio Connection by sending a Radio Connection Reject message with anew PAC value and a wait time for reconnection set as zero. Uponreceiving the Radio Connection Reject message, the UT aborts theconnection establishment procedure and forwards the assigned PAC to theNAS. The NAS then re-initiates the pending procedure. These operationswill now be described in detail in conjunction with FIGS. 15A and 15B.

VI-A. Power ON/Initial Attach

FIGS. 15A and 15B illustrate a message flow diagram for an initialattach operation (e.g., at UT power ON) in accordance with some aspectsof the disclosure. The message flow will be discussed in the context ofa satellite communication system that includes a UT, a BxP/AxP, and aCNCP.

In this example, the UT is initially not attached to a network (block1502 of FIG. 15A). In accordance with the teachings herein, the UT usesPACdefault to start a connection after camping on a cell (block 1504).

In a first operation (1), the UT uses PACdefault to initiate CNCLmobility procedures. Specifically, the UT initiates an Attach procedureand initiates a Radio connection with PACdefault. The correspondingRadio Connection Request also includes an identifier of the UT (UT-ID)and indication that the Radio Connection Request originates at a mobiledevice (Mobile-Signaling).

Upon receiving the Radio Connection Request, at block 1506, the ACPserving the UT assigns a PAC from the valid range of PACs (designatedPACa in this example).

At a second operation (2), the assigned PAC is sent to the UT in a RadioConnection Reject. The PAC value is maintained in UT context. The RadioConnection Reject also includes a wait time variable set to zero,thereby requesting that the UT “immediately” attempt to reconnect.

A new connection is initiated with the assigned PAC (block 1508). At athird operation (3), the UT sends a Radio Connection Request thatincludes the assigned PAC.

At a fourth operation (4), the ACP sends an Initial UT Message to theCore Network Control Plane (CNCP) for a Core Network Interface logicalconnection establishment with the received Attach Request and theassigned PAC value.

In a fifth operation (5) through a seventh operation (7), UT context isestablished between the ACP and the CNCP. CNCL Security is activated inthe fifth operation (5). The CNCP sends an Initial Context Setup Requestincluding the Attach Accept to the ACP in the sixth operation (6). TheAttach Accept includes the same PAC (the PAC received in the Initial UTMessage). In the seventh operation (7), the ACP activates RadioConnection Layer (RCL) security.

The ACP then waits for UT's geographic location (e.g., running a guardtimer). In an eighth operation (8), the UT sends Location Indication(including the UT's GPS location) soon after RCL security activation.The ACP stores the received UT location information (block 1510).

In a ninth operation (9), if the ACP determines that the UT locationdoes not fall under any forbidden area, a connection reconfiguration maybe initiated setting up Radio Signaling Paths (e.g., RSP2) and RadioData Paths (RDPs). The Attach Accept may be piggy-backed in thecorresponding Radio Connection Reconfiguration message. In a tenthoperation (10), the UT sends a Radio Connection Reconfiguration Completeto the ACP.

In an eleventh operation (11), the ACP sends an Initial Context SetupResponse to the CNCP. The UT's CNCL gets the PAI information in theAttach Accept. The CNCL stores the received PAC and compares it againstthe last PAC (in this case PACdefault) to determine the next action. TheCNCL may use the following Table 1 for this purpose.

TABLE 1 UT Action on receiving a new PAC value Old PAC value ReceivedPAC value Action PACdefault PAC other than No update procedurePACdefault PAC other than PAC other than Start update procedurePACdefault (e.g., PACdefault and different PACa) from the old PAC value(e.g., PACb) PACdefault PACdefault No update procedure PAC other thanPACdefault Start update procedure PACdefault

The UT sends a Temporary Network Identifier (TNI) report before sendingan Attach Complete message (block 1512). Thus, in a twelfth operation(12), the UT sends a TNI-Report including the old TNI and the new TNI tothe ACP. Upon reception of this information, the ACP updates the UTlocation information in a Position Database with a new Temporary NetworkIdentifier (block 1514). At a thirteenth operation (13), the UT sendsthe Attach Complete to the CNCP and the procedure ends.

From this point onwards, the UT uses this PAC for subsequent procedures,until a new PAC is assigned by network or the PAC value is reset toPACdefault. A new PAC may be assigned to the UT, for example, viadownlink messages such as Radio Connection Reject, Radio ConnectionReconfiguration, or Radio Connection Release.

VII. Detailed Example for PAC Reassignment

The disclosure relates in some aspects to reassigned a PAC. In someaspects, PAC reassignment may be used to address Issue #2 discussedabove. Several PAC reassignment design options are described belowdepending upon the UT location database design inside the ACP.

VII-A. New ACP does not Require UT Assistance in Retrieving UT LocationInformation

FIGS. 16A and 16B illustrate a message flow diagram for a PACreassignment operation where a UT is served by a new ACP, and where thenew ACP does not require UT assistance in retrieving UT locationinformation. The message flow will be discussed in the context of asatellite communication system that includes a UT, a BxP, a first AxPa,a second AxPb, and a CNCP.

Initially (block 1602), the UT is attach or updated with PACa. Inaddition, default bearers (paths) are established. The UT is inConnection Management (CM) state IDLE and the CNI is released. At somepoint in time, the UT initiates a Service Request (block 1604). In afirst operation (1), the UT sends a Radio Connection Request with thelast registered/updated PAC.

In this example, the network (e.g., the BxP) assigns a new AxP (e.g., anew ACP) for handling this UT (block 1606). For example, the AxP may bechanged from AxPa to AxPb. The new ACP assigns a new PAC (e.g., PACb)for the UT. In a second operation (2), the ACP rejects the RadioConnection by sending a Radio Connection Reject that includes a waittime set to zero and the new PAC value.

Optionally, if the network does not have a centralized UT locationinformation database (which may be accessible from all ACP nodes with aTemporary Network Identifier (TNI) as a key), then the ACP may attemptto retrieve UT location information using the UT's old PAC value andTemporary Network Identifier before sending the connection reject.

The Service Request procedure is aborted due to the change in PAinformation (block 1608). The UT's RCL reports the failure of theconnection establishment procedure to the UT's CNCL. The failure beingindicated as result of a cause “PA information changed.” The RCL alsoforwards the new PAC value (PACb) to the CNCL. The UT then initiates aPaging Area Update (PAU) procedure with bearer re-establishment.

In a third operation (3), the UT sends a Radio Connection Request withthe new PAC value to the ACP. In a fourth operation (4), the ACP sends aRadio Connection Setup with the new PAC value to the UT. In a fifthoperation (5), the UT sends a Radio Connection Setup Complete with aPaging Area Update Request to the ACP. In a sixth operation (6), the ACPsends an Initial UT Message to the CNCP with the received PAU Requestand the PAC value. In a seventh operation (7), the CNCP sends an InitialContext Setup Request including a PAU Accept to the ACP. In an eighthoperation (8), the ACP activates Radio Connection Layer (RCL) security.

In a ninth operation (9), the UT sends a Location Indication to the ACP.The ACP stores the received UT location information (block 1610).

In a tenth operation (10), if the ACP determines that the UT locationdoes not fall under any forbidden area, the ACP sends a Radio ConnectionReconfiguration with a PAU Accept to the UT. In an eleventh operation(11), the UT sends a Radio Connection Reconfiguration Complete includingthe PAU accept to the ACP. In a twelfth operation (12), the ACP sends anInitial Context Setup Response to the CNCP.

In an optional mobile temporary identifier relocation operation (block1612), the UT sends a Temporary Network Identifier (TNI) report beforesending a PAU Complete message (block 1614). Thus, in a thirteenthoperation (13), the UT sends a TNI-Report including the old TNI and thenew TNI to the ACP. Upon reception of this information, the ACP updatesthe UT location information in a Position Database with a new TemporaryNetwork Identifier (block 1616). Here, if a previous TNI is received,the existing entry for the UT is updated. Otherwise, a new entry withTNI is created. At a fourteenth operation (14), the UT sends the PAUComplete to the CNCP and the procedure ends.

If the network has a centralized UT location information database (whichis accessible from all ACP nodes with a Temporary Network Identifier asa key), then the ACP may attempt to retrieve the UT location informationusing only a Temporary Network Identifier Connection establishment and aPAU procedure completion using CNCL/RCL protocols.

VII-B. New ACP Requires UT Assistance in Retrieving UT LocationInformation (Old PAC Value is not ACP Controlled)

FIGS. 17A and 17B illustrate a message flow diagram for a PACreassignment operation where a UT is served by a new ACP, and the newACP uses UT assistance in retrieving UT location information. In thiscase, the reporting of the old PAC value in a Radio Connection Requestis not ACP controlled. For example, the UT may send both the new PAC andthe old PAC on every PAC change. The message flow will be discussed inthe context of a satellite communication system that includes a UT, aBxP, a first AxPa, a second AxPb, and a CNCP.

Blocks 1702, 1704, 1706, and 1708 of FIG. 17 correspond to blocks 1602,1604, 1606, and 1608 of FIG. 16A discussed above. In addition, a firstoperation (1) and a second operation (2) of FIG. 17 correspond to thefirst operation (1) and the second operation (2) of FIG. 16A discussedabove.

In a third operation (3), the UT sends a Radio Connection Request to theACP. The Radio Connection Request may be sent with IFs for both the newPAC value (e.g., PACb) and the old PAC value (e.g., PACa). The ACP maythen attempt to retrieve the UT location information using the old PACand the Temporary Network Identifier (block 1710).

The connection establishment and the PAU procedure completion may thenbe done as follows. In a fourth operation (4), the ACP sends a RadioConnection Setup to the UT. In a fifth operation (5), the connection isestablished, the PAU procedure is completed, and bearers are resumed.

VII-C. New ACP Requires UT Assistance in Retrieving UT LocationInformation (Old PAC Value is ACP Controlled)

FIGS. 18A and 18B illustrate a message flow diagram for a PACreassignment operation where a UT is served by a new ACP, and the newACP uses UT assistance in retrieving UT location information. In thiscase, reporting of an old PAC value in a Radio Connection Request may beACP controlled. For example, the UT may send both the new PAC and theold PAC in response to a request from the network. The message flow willbe discussed in the context of a satellite communication system thatincludes a UT, a BxP, a first AxPa, a second AxPb, and a CNCP.

Blocks 1802, 1804, and 1806 of FIG. 18A correspond to blocks 1702, 1704,and 1706 of FIG. 17 discussed above. In addition, a first operation ofFIG. 18A corresponds to the first operation (1) of FIG. 17 discussedabove.

In a first alternative approach (block 1808) where the UT locationdatabase is not centralized, the new ACP retrieves the UT locationbefore rejecting the connection. Thus, the ACP first retrieves the UTlocation information (block 1810) and then, in a second operation (2),the ACP sends a Radio Connection Reject to the UT. In this case, anOldPACneeded IF of the Radio Connection Reject indicates that the oldPAC is not needed.

In a second alternative approach (block 1812) where the UT locationdatabase is not centralized, the new ACP retrieves the UT location atthe next connection request. Thus, in a third operation (3), the ACPsends a Radio Connection Reject to the UT where the OldPACneeded IF ofthe Radio Connection Reject indicates that the old PAC is needed.

Block 1814 of FIG. 18B correspond to block 1708 of FIG. 17 discussedabove.

In a first alternative approach (block 1816) where OldPACneeded wasFALSE, in a fourth operation (4), the UT sends a Radio ConnectionRequest that includes the new PAC to the ACP.

In a second alternative approach (block 1818) where OldPACneeded wasTRUE, in a fifth operation (5), the UT sends a Radio Connection Requestthat includes the new PAC and the old PAC to the ACP. The ACP may thenattempt to retrieve the UT location information using the old PAC andthe Temporary Network Identifier (block 1820).

The connection establishment and the PAU procedure completion may thenbe done as follows. In a sixth operation (6), the ACP sends a RadioConnection Setup to the UT. In a seventh operation (7), the connectionis established, the PAU procedure is completed, and bearers are resumed.

In the sequence of FIGS. 18A and 18B, ACP can retrieve UT locationinformation either at the second operation (2) or the fifth operation(5) depending on the network implementation of the location database.Reporting of the old PAC may be controlled by network as discussedabove.

VII-D. Inter Administrative Region Connection Handoff

FIGS. 19A-19E illustrate a message flow diagram for anInter-Administrative Region Connection Handoff in accordance with someaspects of the disclosure. Here, the UT is served by and the PAC isreassigned. The message flow will be discussed in the context of asatellite communication system that includes a UT, a source BxP, atarget BxP, a source AxP, a target AxP, a source LxP, a target LxP, aCNCP, and a CNUP.

With reference to FIG. 19A, initially, the UT is Attached or Updated anddefault bearers (paths) are established. The UT is in ConnectionManagement state CONNECTED. Forward link (FL) and reverse link trafficare indicated by bracket 1902.

Bracket 1904 indicates handoff preparation operations at a firstoperation (1) through a ninth operation (9). The Network initiates aConnection Handoff relocating AxP. In the first operation (1) and thesecond operation (2), the source AxP make a handoff decision and sends aHandoff Required to the CNCP. In the third operation (3), the CNCP sendsa Handoff Request to the target AxP. In the fourth operation (4) and thefifth operation (5), the target AxP, the target AxP performs admissioncontrol (e.g., target AxP derives a new K_(p)), and sends a HandoffRequest Acknowledge to the CNCP. In some aspects, this may be only forindirect forwarding of data (i.e., via CNI). In the first part of thesixth operation (6A), the CNCP sends a Create Indirect Data ForwardingTunnel Request to the CNUP. In the second part of the sixth operation(6B), the CNUP sends a Create Indirect Data Forwarding Tunnel Responseto the CNCP. In the seventh operation (7), the CNCP sends a HandoffCommand to the source AxP. A new PAC may be assigned to UT. In the firstpart of the eighth operation (8A), the source AxP sends a RadioConnection Reconfiguration including the new PAC to the source BxP. Inthe second part of the eighth operation (8B), the source BxP sends theRadio Connection Reconfiguration including the new PAC to the source UT.The UT thus derives the new K_(AXP) at the ninth operation (9).

Referring to FIG. 19B, the bracket 1906 indicates handoff executionoperations at a tenth operation (10) through a sixteenth operation (16).Here, the UT applies the handoff configuration and sends a RadioReconfiguration Complete to the AxP. In the tenth operation (10), the UTreset its Media Access Control (MAC) and RLC and acquires a new cell. Inthe first part of the eleventh operation (11A), the source AxP sends aStatus Transfer message to the CNCP. In the second part of the eleventhoperation (11B), the CNCP sends a Status Transfer message to the targetAxP. The bracket 1908 indicated packet data forwarding. In some aspects,the forwarding from the source AxP to the target AxP may be only fordirect forwarding of data (i.e., via an appropriate interface). In someaspects, the forwarding from the source AxP to the CNUP may be only fordirect forwarding of data (i.e., via the CNI). In the twelfth operation(12), the target AxP buffers data from the source AxP. In the thirteenthoperation (13), the UT sends a Random Access Preamble (e.g., using acontention RACH preamble) to the target BxP. In the fourteenth operation(14), the target BxP sends a Random Access Response to the UT. ThisResponse may include a contention RACH preamble ID, PA information, anRL Grant, and a temporary Radio Network Identifier.

As indicated by block 1910, there may be a chance of collision unless adedicated preamble signature is used. In the first part of the fifteenthoperation (15A), the UT sends a Radio Connection ReconfigurationComplete to the target BxP. This message may include a Radio NetworkIdentifier MAC element. In some aspects, the target BxP may parse theRadio Network Identifier MAC element and forward the Radio message tothe correct AxP. In the second part of the fifteenth operation (15B),the target BxP sends a Radio Connection Reconfiguration Complete to thetarget AxP. In some aspects, the target AxP may send a Handoff Notifymessage to the CNCP at this time (see the nineteenth operation). In thesixteenth operation (16), the target BxP sends an RL Grant to the UT.

The UT's CNCL then starts a Paging Area Update procedure for a new PAC.At block 1912, handoff completion and the new PAC are reported to theCNCL. At block 1914, a PAU is initiated with update type “PA Updating.”

Referring to FIGS. 19C and 19D, the bracket 1916 indicates handoffcompletion operations at a seventeenth operation (17) through a twentyfifth operation (25B). Here, status description and data forwarding isperformed between network nodes to complete handoff processing. Theseventeenth operation (17) is optional. In the first part of theseventeenth operation (17A), the UT sends a Packet Data Status Report tothe target BxP. This message may include a list of missing or receivedFL Packet Data protocol data units. In the second part of theseventeenth operation (17B), the target BxP sends a Packet Data StatusReport to the target AxP. Bracket 1918 shows the FL packet data.

The eighteenth operation (18) is optional. In a first part of theeighteenth operation (18A), the target AxP sends a Packet Data StatusReport to the target BxP. This message may include a list of missing orreceived RL Packet Data protocol data units. In a second part of theeighteenth operation (18B), the target BxP sends a Packet Data StatusReport to the UT. Bracket 1920 shows the RL packet data. In thenineteenth operation (19), the target AxP sends a Handoff Notify to theCNCP. In the twentieth operation (20), the CNCP sends a Modify BearerRequest to the CNUP.

Referring to FIG. 19D, in the twenty first operation (21), the CNUPswitches the FL data path. The bracket 1922 shown the end markerpacket(s). In some aspects, the end marker packets from the source AxPto the CNUP may be only for indirect forwarding of data (i.e., via theCNI). In some aspects, the end marker packets from the source AxP to thetarget AxP may be only for indirect forwarding of data (i.e., via anappropriate interface). In the twenty second operation (22), the CNUPsends a Modify Bearer Response to the CNCP. In a first part of thetwenty third operation (23A), the CNCP sends a UT Context ReleaseCommand to the source AxP. In a second part of the twenty thirdoperation (23B), the source AxP sends a UT Context Release Complete tothe CNCP. In the twenty fourth operation (24), the source AxP releasesthe UT resources and context. In a first part of the twenty fifthoperation (25A), the CNCP sends a Delete Indirect Data Forwarding TunnelRequest to the CNUP. In a second part of the twenty fifth operation(25B), the CNUP sends a Delete Indirect Data Forwarding Tunnel Responseto the CNCP.

Referring to FIG. 19E, the bracket 1924 shown the FL packet data and theRL packet data after the handoff. In a twenty sixth operation (26A)through a twenty seventh operation (27C), Paging Area Update Request andAccept messages are carried in direct transfer messages between the UTand the CNCP. In a first part of the twenty sixth operation (26A), theUT sends an UL Information Transfer with a PAU Request to the targetBxP. The PAU Request includes the PAC (PACa) and an indication of “PAUpdating.” In a second part of the twenty sixth operation (26B), thetarget BxP sends an UL Information Transfer with a PAU Request to thetarget AxP. In a third part of the twenty sixth operation (26C), thetarget AxP sends an UL CNCL Transport with a new PAC (PACb) and a PAURequest to the CNCP. In a first part of the twenty seventh operation(27A), the CNCP sends a DL Transport with a PAU Accept to the targetAxP. In a second part of the twenty seventh operation (27B), the targetAxP sends a DL Information Transfer with a PAU Accept and the new PAC(PACb) to the target BxP. In a third part of the twenty seventhoperation (27C), the target BxP sends a DL Information Transfer with thePAU Accept and the new PAC to the UT.

At block 1926, if the UT received a new Global Temporary NetworkIdentifier (GTNI) in a Paging Area Update Accept message, the UT sends aTemporary Network Identifier (TNI) report to the AxP before sending aRegister Complete. In a first part of the twenty eighth operation (28A),the UT sends a TNI Report with the old TNI and the new TNI to the targetBxP. In a second part of the twenty eighth operation (28B), the targetBxP sends a TNI Report with the old TNI and the new TNI to the targetAxP. The AxP then updates the UT location database with the newTemporary Network Identifier (block 1928). In a first part of the twentyninth operation (29A), the UT sends an UL Information Transfer with aPAU Accept to the target BxP. In a second part of the twenty ninthoperation (29B), the target BxP sends an UL Information Transfer with aPAU Accept to the target AxP. In a third part of the twenty ninthoperation (29C), the target AxP sends an UL CNCL Transport with the newPAC (PACb) and the PAU Accept to the CNCP.

VIII. Detailed Examples for Forbidden Area Handling

The disclosure relates in some aspects to defining a set of PA valuesthat are associated with one or more forbidden areas. These values maybe referred to as forbidden PACs (PACf). In some aspects, PACdefault maybe used to address Issue #3 discussed above.

The Core Network Control Plane (CNCP) is aware of the forbidden PA set.Whenever a UT's GPS location falls in any of the forbidden areas, theACP assigns a PAC from the Forbidden PA Set to the UT and releases theconnection. If a registered UT initiates a PAU Request due to a changein the PAC value, the CNCP rejects the PAU and releases the connection.If a deregistered UT initiates an Attach Request, the CNCP rejects theAttach and releases the connection.

Forbidden area handling issues may arise in various scenarios. Forexample, a UT may start an Attach procedure in a forbidden zone. Asanother example, a registered UT may move into a forbidden zone whilethe UT is in IDLE mode. As yet another example, a registered UT may moveinto a forbidden zone while the UT is in CONNECTED mode. Also, a UT mayreattempt to obtain service after a lapse of a restriction (e.g., basedon a time threshold and/or a distance threshold). Several options forconnection release signaling (between a UT and the ACP) when a UT's GPSlocation falls in one of the forbidden zone will now be described.

VIII-A. Forbidden Area Handling Option 1

In a first forbidden area handling option (Option 1), a UT is assigned anew PAC from the set of forbidden PAs using a reconfiguration procedurefollowed by a connection release.

VIII-A-1. UT Starts Attach Procedure in Forbidden Area

FIGS. 20A and 20B illustrate a message flow diagram for an initialattach (e.g., a power ON attach) procedure in a forbidden area where aforbidden PAC is assigned to a UT in accordance with some aspects of thedisclosure. The message flow will be discussed in the context of asatellite communication system that includes a UT, a BxP, an AxP, and aCNCP.

Referring to FIG. 20A, the UT is initially not attached to a network(block 2002). As discussed herein, the UT uses PACdefault to start aconnection (block 2004).

In a first operation (1), after camping on a cell, the UT usesPACdefault to initiate CNCL mobility procedures. Specifically, the UTinitiates an Attach procedure and initiates a Radio connection bysending a Radio Connection Request including PACdefault to the BxP/AxP.

Upon receiving the Radio Connection Request, at block 2006, the ACPserving the UT assigns a PAC from the valid range of PACs (designatedPACa in this example).

At a second operation (2), the assigned PAC is sent to the UT in a RadioConnection Reject. The PAC value is maintained in UT context. The RadioConnection Reject includes a wait time variable set to zero, therebyrequesting that the UT “immediately” attempt to reconnect.

The Attach procedure is aborted due to the change in PA information(block 2008). The UT's RCL reports the failure of the connectionestablishment procedure to the UT's CNCL. The failure being indicated asresult of a cause “PA information changed.” A new Radio connection isinitiated with the assigned PAC. At a third operation (3), the UT sendsa Radio Connection Request that includes the assigned PAC.

At a fourth operation (4), the ACP sends an Initial UT Message to theCore Network Control Plane (CNCP) for a Core Network Interface logicalconnection establishment with the received Attach Request and theassigned PAC value.

In a fifth operation (5) through a seventh operation (7), UT context isestablished between the ACP and the CNCP. CNCL Security is activated inthe fifth operation (5). The CNCP sends an Initial Context Setup Requestincluding the Attach Accept to the ACP in the sixth operation (6). TheAttach Accept includes the same PAC (the PAC received in the Initial UTMessage). In the seventh operation (7), the ACP activates RadioConnection Layer (RCL) security.

The ACP then waits for the UT's geographic location. In an eighthoperation (8), the UT sends Location Indication (including the UT's GPSlocation) following the RCL security activation. The ACP stores thereceived UT location information (block 2010). The ACP determines thatthe UT location falls under any forbidden area and assigns a PAC fromthe Forbidden PA Set and sends new PAC using a reconfigurationprocedure. In addition, the ACP indicates when the UT is to start usingthe new PAC. To this end, in a ninth operation (9), the ACP sends aRadio Connection Reconfiguration to the UT. The Radio ConnectionReconfiguration includes PACf and an indication to commence an updateprocedure once the UT is released.

The UT stores the received PACf and waits for a trigger (e.g., aconnection release) to start using the stored PAC (block 2012). In atenth operation (10), the UT sends a Radio Connection ReconfigurationComplete to the ACP.

In an eleventh operation (11), the ACP sends an Initial Context SetupFailure to the CNCP. The Initial Context Setup Failure includes aMiscellaneous Cause value of “Unspecified.” The CNCP initiates aconnection release upon receiving this message with the mentioned causevalue. Accordingly, in a twelfth operation (12), the CNCP sends a UTContext Release Command to the ACP.

The ACP defines restriction criteria in terms of a restricted region(block 2014). For example, a restriction criterion may be defined by oneor a list of an ellipsoid point (e.g., a center point) and a distance(e.g., a radius) from the ellipsoid point. Alternatively, or inaddition, a restriction criterion may be defined in terms of a durationthreshold (e.g., a period of time after detection of a UT in arestricted area). Use of a restricted area list is intended to beindicative, not exhaustive, of a manner in which a geographical area canbe defined. Thus, other techniques could be used to send area (zone)information in a Radio message (e.g., a Radio Connection Releasemessage).

The ACP performs a connection release with information for a subsequentUpdate procedure towards mobility management. In a thirteenth operation(13) and a fourteenth operation (14), the ACP sends a Radio ConnectionRelease to the UT and a UT Context Release Complete to the CNCP.

The Radio Connection Release may include one or more of: servicerestriction information (e.g., a flag indicating service is restricted);an optional time duration-based restriction threshold, or an optionalrestricted area definition. The Restricted Area may be defined as atuple {GPS coordinate, distance from that coordinate}. As mentionedabove, the ACP can provide a list of at least one restricted area havingat least one area definition.

A UT checks its GPS location against the defined restricted region. Ifthe UT's location falls within any of the restricted areas, the UTshould deem the service restriction to be active. If the UT's locationdoes not fall within any restricted area, the UT may deem that theservice restriction has lapsed and therefore initiate an Attachprocedure.

Upon receiving the Radio Connection Release, the UT aborts the Attachprocedure, starts a counter for the duration and distance restriction,and starts a new connection with PACf (block 2016). In other words, oncethe connection release is completed, the UT starts using PACf andtriggers an Attach procedure.

In a fifteenth operation (15), the UT sends a Radio Connection Requestwith PACf to the ACP. The Request is serviced by the ACP that handlesforbidden PACs (block 2018). In a sixteenth operation (16), the ACPsends a Radio Connection Setup to the UT. In a seventeenth operation(17), the UT sends a Radio Connection Setup Complete with an AttachRequest to the ACP. In an eighteenth operation (18), the ACP sends anInitial UT Message for CNI logical connection establishment to the CNCPwith the received Attach Request and the PACf. There is no defaultbearer in this case (block 2020). In a nineteenth operation (19), theCNCP sends a DL CNCL Transport including an Attach Reject to the ACP.The Attach Reject includes the PACf and an indication of the cause(“cause #12, PA not allowed”). In a twentieth operation (20), the ACPsends a DL Information Transfer including the Attach Reject to the UT.The UT adds PACf to its forbidden list and the procedure ends (block2022). In a twenty first operation (21), the connection is released.

The UT's CNCL does not attempt to reconnect until a designated event(trigger) occurs (block 2024). For example, the CNCL may wait until anew PAC is received. As another example, the CNCL may wait until theforbidden list is reset (e.g., when the UT is powered off, when the UT'ssubscriber information module is removed, or periodically).

VIII-A-2. Registered UT Moves into a Forbidden Area During IDLE

FIGS. 21A and 21B illustrate a message flow diagram for a procedurewhere a UT moves from a normal service area to a forbidden area while inIDLE mode and where a forbidden PAC is assigned to a UT in accordancewith some aspects of the disclosure. The message flow will be discussedin the context of a satellite communication system that includes a UT, aBxP, an AxP, and a CNCP.

Referring initially to FIG. 21A, a UT in Connection Management stateIDLE is Attached/Updated and default bearers are established (block2102). When the UT requires a connection for sending a UT locationreport, the UT's RCL send a new trigger to the UT's CNCL to initiateconnection establishment for a location update (block 2104). The CNCLinitiates a PAU Request with type “PA Updating” and an Active flag setas ‘1.’ The message is integrity protected using the current securitycontext in the CNCL (message contains MAC-CNCL).

In a first operation (1), the UT sends a Radio Connection Request thatincludes the assigned PAC (PACa) to the ACP. In a second operation (2),the ACP sends a Radio Connection Setup to the UT. In a third operation(3), the UT sends a Radio Connection Setup Complete with the PAU Requestto the ACP. In a fourth operation (4), the ACP sends an Initial UTMessage to the CNCP with the received PAU Request and the PAC value.

The CNCP does an integrity check on PAU Request message. If theintegrity check passes, this means that CNCL-CNCP security is ON. TheCNCP therefore requests an Initial Context Setup in the AxP. Thus, in afifth operation (5), the CNCP sends an Initial Context Setup Requestincluding a PAU Accept to the ACP. In a sixth operation (6), the ACPactivates Radio Connection Layer (RCL) security. The AxP waits for theUT's location information after activating RCL security.

In a seventh operation (7), the UT sends a Location Indication to theACP after RCL security activation. The ACP updates a location databasewith the received UT location information (block 2106). Upon determiningthat the UT location falls under a forbidden area, the ACP assigns a PACfrom the Forbidden PA Set for the UT. Consequently, the ACP sends a newPAC to the UT using a reconfiguration procedure, indicating when the UTis to start using the new PAC. To this end, in an eighth operation (8),the ACP sends a Radio Connection Reconfiguration to the UT. The RadioConnection Reconfiguration includes PACf and an indication to commencean update procedure once the UT is released.

The UT stores the received PACf and waits for a trigger (e.g., aconnection release) to start using the stored PAC (block 2108). In aninth operation (9), the UT sends a Radio Connection ReconfigurationComplete to the ACP.

In a tenth operation (10), the ACP sends an Initial Context SetupFailure to the CNCP. The Initial Context Setup Failure includes aMiscellaneous Cause value of “Unspecified.” The CNCP initiates aconnection release upon receiving this message with the mentioned causevalue. Accordingly, in an eleventh operation (11), the CNCP sends a UTContext Release Command to the ACP.

The ACP defines a restriction criteria in terms of a restricted regionas discussed above (block 2110). The ACP performs a connection releasewith information for a subsequent Update procedure towards mobilitymanagement. In a twelfth operation (12) and a thirteenth operation (13),the ACP sends a Radio Connection Release to the UT and a UT ContextRelease Complete to the CNCP.

The Radio Connection Release may include one or more of: servicerestriction information (e.g., a flag indicating service is restricted);an optional time duration-based restriction threshold, or an optionalrestricted area definition as discussed above. A UT can thereby checkits GPS location against the defined restricted region.

Upon receiving the Radio Connection Release, the UT aborts the PAUprocedure, starts a counter for the duration and distance restriction,and starts a new connection with PACf (block 2112). In other words, oncethe connection release is completed, the UT starts using PACf andtriggers a PAU procedure.

In a fourteenth operation (14), the UT sends a Radio Connection Requestwith PACf to the ACP. The Request is serviced by the ACP that handlesforbidden PACs (block 2114). In a fifteenth operation (15), the ACPsends a Radio Connection Setup to the UT. In a sixteenth operation (16),the UT sends a Radio Connection Setup Complete with a PAU Request to theACP. In a seventeenth operation (17), the ACP sends an Initial UTMessage for CNI logical connection establishment to the CNCP with thereceived PAU Request and the PACf. There is no default bearer in thiscase (block 2116). In an eighteenth operation (18), the CNCP sends a DLCNCL Transport including an Attach Reject to the ACP. The Attach Rejectincludes the PACf and an indication of the cause (“cause #12, PA notallowed”). In a nineteenth operation (19), the ACP sends a DLInformation Transfer including the PAU Reject to the UT. The UT addsPACf to its forbidden list and the procedure ends (block 2118). In atwentieth operation (20), the connection is released.

VIII-A-3. Registered UT Moves into a Forbidden Area During CONNECTED

FIGS. 22A and 22B illustrate a message flow diagram for a procedurewhere a UT moves from a normal service area to a forbidden area while inCONNECTED mode and where a forbidden PAC is assigned to a UT inaccordance with some aspects of the disclosure. The message flow will bediscussed in the context of a satellite communication system thatincludes a UT, a BxP, an AxP, and a CNCP.

Referring initially to FIG. 22A, the UT is in Connection Managementstate CONNECTED with active data bearers (block 2202). The UT reportslocation information based on a Location Change Threshold defined at thetime of Radio Connection setup. Thus, at some point in time, the UT'sRCL triggers a location update due to motion of the UT (block 2204).Accordingly, in a first operation (1), the UT sends a LocationIndication to the ACP.

The remaining operations of FIGS. 22A and 22B are similar tocorresponding operations of FIGS. 21A and 21B discussed above.Specifically, blocks 2206, 2208, 2210, 2212, 2214, 2216, and 2218correspond to blocks 2106, 2108, 2110, 2112, 2114, 2116, and 2118,respectively. In addition, the second though fourteenth operations ofFIGS. 22A and 22B correspond to the eighth through twentieth operationsof FIGS. 21A and 21B, respectively.

VIII-B. Forbidden Handling Option 2

In a second forbidden area handling option (Option 2), a UT is initiallyassigned an invalid (e.g., a default) PAC. The UT is forced toinvalidate the assigned PAC on connection release and do an Attach orPAU procedure after connection release.

VII-B-1. UT Starts Attach Procedure in Forbidden Area

FIGS. 23A and 23B illustrate a message flow diagram for an initialattach (e.g., a power ON attach) procedure in a forbidden area where aninvalid PAC is initially assigned to a UT in accordance with someaspects of the disclosure. The message flow will be discussed in thecontext of a satellite communication system that includes a UT, a BxP,an AxP, and a CNCP.

Referring to FIG. 23A, the UT is initially not attached to a network(block 2302). As discussed herein, the UT uses PACdefault to start aconnection (block 2304).

In a first operation (1), after camping on a cell, the UT usesPACdefault to initiate CNCL mobility procedures. Specifically, the UTinitiates an Attach procedure and initiates a Radio connection bysending a Radio Connection Request including PACdefault to the BxP/AxP.

Upon receiving the Radio Connection Request, at block 2306, the ACPserving the UT assigns a PAC from the valid range of PACs (designatedPACa in this example).

At a second operation (2), the assigned PAC is sent to the UT in a RadioConnection Reject. The PAC value is maintained in UT context. The RadioConnection Reject includes a wait time variable set to zero, therebyrequesting that the UT “immediately” attempt to reconnect.

The Attach procedure is aborted due to the change in PA information(block 2308). The UT's RCL reports the failure of the connectionestablishment procedure to the UT's CNCL. The failure being indicated asresult of a cause “PA information changed.” A new Radio connection isinitiated with the assigned PAC. At a third operation (3), the UT sendsa Radio Connection Request that includes the assigned PAC.

At a fourth operation (4), the ACP sends an Initial UT Message to theCore Network Control Plane (CNCP) for a Core Network Interface logicalconnection establishment with the received Attach Request and theassigned PAC value.

In a fifth operation (5) through a seventh operation (7), UT context isestablished between the ACP and the CNCP. CNCL Security is activated inthe fifth operation (5). The CNCP sends an Initial Context Setup Requestincluding an Attach Accept to the ACP in the sixth operation (6). TheAttach Accept includes the same PAC (the PAC received in the Initial UTMessage). In the seventh operation (7), the ACP activates RadioConnection Layer (RCL) security.

The ACP then waits for the UT's geographic location. In an eighthoperation (8), the UT sends Location Indication (including the UT's GPSlocation) following the RCL security activation. In a ninth operation(9), the ACP determines that the UT location falls under a forbiddenarea and sends an Initial Context Setup Failure to the CNCP. The InitialContext Setup Failure includes a Miscellaneous Cause value of“Unspecified.” The CNCP initiates a connection release upon receivingthis message with the mentioned cause value. Accordingly, in a tenthoperation (10), the CNCP sends a UT Context Release Command to the ACP.

The ACP initiates a connection release forcing the UT to invalidate itsassigned PAC (block 2310). As discussed above, the ACP definesrestriction criteria in terms of a restricted region. In an eleventhoperation (11) and a twelfth operation (12), the ACP sends a RadioConnection Release to the UT and a UT Context Release Complete to theCNCP. The UT is thus forced to do an Attach procedure after theconnection release. As discussed above, the Radio Connection Release mayinclude one or more of: service restriction information (e.g., a flagindicating service is restricted); an optional time duration-basedrestriction threshold, or an optional restricted area definition.

Upon receiving the Radio Connection Release, the UT aborts the Attachprocedure, starts a counter for the duration and distance restriction,and starts a new connection with an invalid PAC (block 2312). In otherwords, once the connection release is completed, the UT starts using theinvalid PAC (PACinv) and triggers an Attach procedure.

In a thirteenth operation (13) through a fifteenth operation (15), aRadio connection is initiated with PAC information including the old PAC(PACa) and the new PAC (PACinv). The ACP may do specific handling forthe scenario where the oldPAC=the last updated PAC and the PAC=PACinv.For example, the UT may be serviced by the ACP that handled the oldPAC.In the thirteenth operation (13), the UT sends a Radio ConnectionRequest with PACinv and PACa to the ACP.

The Request is serviced by the ACP corresponding to the old PAC (block2314). However, a PAC from the set of forbidden PACs (e.g., PACf) issent over the CNI. In a fourteenth operation (14), the ACP sends a RadioConnection Setup to the UT. In a fifteenth operation (15), the UT sendsa Radio Connection Setup Complete with an Attach Request to the ACP. Ina sixteenth operation (16), the ACP sends an Initial UT Message for CNIlogical connection establishment to the CNCP with the received AttachRequest and the PACf. There is no default bearer in this case (block2316). In a seventeenth operation (17), the CNCP finds the received PACto be part of the forbidden PA set and therefore sends a DL CNCLTransport including an Attach Reject to the ACP. The Attach Rejectincludes an indication of the cause (“cause #12, PA not allowed”). In aneighteenth operation (18), the ACP sends a DL Information Transferincluding the Attach Reject to the UT. The UT adds PACinv to its list offorbidden tracking areas for regional provision of service, and theprocedure ends (block 2318). In a nineteenth operation (19), theconnection is released.

The UT's CNCL does not attempt to reconnect until a designated event(trigger) occurs (block 2320). For example, the CNCL may wait until anew PAC is received. As another example, the CNCL may wait until theforbidden list is reset (e.g., when the UT is powered off, when the UT'ssubscriber information module is removed, or periodically).

VIII-B-2. Registered UT Moves into a Forbidden Area During IDLE

FIGS. 24A and 24B illustrate a message flow diagram for a procedurewhere a UT moves from a normal service area to a forbidden area while inIDLE mode and where an invalid PAC is used by a UT in accordance withsome aspects of the disclosure. The message flow will be discussed inthe context of a satellite communication system that includes a UT, aBxP, an AxP, and a CNCP.

Referring initially to FIG. 24A, a UT in Connection Management stateIDLE is Attached/Updated and default bearers are established (block2402). When the UT requires a connection for sending a UT locationreport, the UT's RCL send a new trigger to the UT's CNCL to initiateconnection establishment for a location update (block 2404). The CNCLinitiates a PAU Request with type “PA Updating” and an Active flag setas ‘1.’ The message is integrity protected as discussed above.

In a first operation (1), the UT sends a Radio Connection Request thatincludes the assigned PAC (PACa) to the ACP. In a second operation (2),the ACP sends a Radio Connection Setup to the UT. In a third operation(3), the UT sends a Radio Connection Setup Complete with the PAU Requestto the ACP. In a fourth operation (4), the ACP sends an Initial UTMessage to the CNCP with the received PAU Request and the PAC value. TheCNCP does an integrity check on the PAU Request as discussed above. In afifth operation (5), the CNCP sends an Initial Context Setup Requestincluding a PAU Accept to the AxP. In a sixth operation (6), the ACPactivates Radio Connection Layer (RCL) security. The AxP waits for theUT's location information after activating RCL security.

In a seventh operation (7), the UT sends a Location Indication to theACP after RCL security activation. The ACP updates a location databasewith the received UT location information (block 2406).

In a ninth operation (9), the ACP determines that the UT location fallsunder a forbidden area and sends an Initial Context Setup Failure to theCNCP. The Initial Context Setup Failure includes a Miscellaneous Causevalue of “Unspecified.” The CNCP initiates a connection release uponreceiving this message with the mentioned cause value. Accordingly, in atenth operation (10), the CNCP sends a UT Context Release Command to theACP.

The ACP initiates a connection release forcing the UT to invalidate itsassigned PAC and perform a PAU procedure after the connection release(block 2408). As discussed above, the ACP defines restriction criteriain terms of a restricted region. In an eleventh operation (11) and atwelfth operation (12), the ACP sends a Radio Connection Release to theUT and a UT Context Release Complete to the CNCP. As discussed above,the Radio Connection Release may include one or more of: servicerestriction information (e.g., a flag indicating service is restricted);an optional time duration-based restriction threshold, or an optionalrestricted area definition.

Upon receiving the Radio Connection Release, the UT aborts the PAUprocedure, starts a counter for the duration and distance restriction,and starts a new connection with an invalid PAC (block 2410). In otherwords, once the connection release is completed, the UT starts using theinvalid PAC (PACinv) and triggers a PAU procedure.

In a thirteenth operation (13) through a fifteenth operation (15), aRadio connection is initiated with PAC information including the old PAC(PACa) and the new PAC (PACinv). The ACP may do specific handling forthe scenario where the oldPAC=the last updated PAC and the PAC=PACinv.For example, the UT may be serviced by the ACP that handled the oldPAC.In the thirteenth operation (13), the UT sends a Radio ConnectionRequest with PACinv and PACa to the ACP.

The Request is serviced by the ACP corresponding to the old PAC (block2412). However, a PAC from the set of forbidden PACs (e.g., PACf) issent over the CNI. In a fourteenth operation (14), the ACP sends a RadioConnection Setup to the UT. In a fifteenth operation (15), the UT sendsa Radio Connection Setup Complete with a PAU Request to the ACP. In asixteenth operation (16), the ACP sends an Initial UT Message for CNIlogical connection establishment to the CNCP with the received PAURequest and the PACf. There is no default bearer in this case (block2414). In a seventeenth operation (17), the CNCP finds the received PACto be part of the forbidden PA set and therefore sends a DL CNCLTransport including a PAU Reject to the ACP. The Attach Reject includesan indication of the cause (“cause #12, PA not allowed”). In aneighteenth operation (18), the ACP sends a DL Information Transferincluding the PAU Reject to the UT. The UT adds PACinv to its list offorbidden tracking areas for regional provision of service, and theprocedure ends (block 2416). In a nineteenth operation (19), theconnection is released.

VIII-B-3. Registered UT Moves into a Forbidden Area During CONNECTED

FIGS. 25A and 25B illustrate a message flow diagram for a procedurewhere a UT moves from a normal service area to a forbidden area while inCONNECTED mode and where a forbidden PAC is assigned to a UT inaccordance with some aspects of the disclosure. The message flow will bediscussed in the context of a satellite communication system thatincludes a UT, a BxP, an AxP, and a CNCP.

Referring initially to FIG. 25A, the UT is in Connection Managementstate CONNECTED with active data bearers (block 2502). The UT reportslocation information based on a Location Change Threshold defined at thetime of Radio Connection setup. Thus, at some point in time, the UT'sRCL triggers a location update due to motion of the UT (block 2504).Accordingly, in a first operation (1), the UT sends a LocationIndication to the ACP.

The remaining operations of FIGS. 25A and 25B are similar tocorresponding operations of FIGS. 24A and 24B discussed above.Specifically, blocks 2506, 2508, 2510, 2512, 2514, 2516, and 2518correspond to blocks 2406, 2408, 2410, 2412, 2414, 2416, and 2418,respectively. In addition, the second though twelfth operations of FIGS.25A and 25B correspond to the eighth through nineteenth operations ofFIGS. 24A and 24B, respectively.

VIII-C. UT Service Recovery after Restriction Lapse

FIGS. 26A and 26B illustrate a message flow diagram for a procedurewhere a UT invokes a reattempt for service after a lapse of arestriction in accordance with some aspects of the disclosure. Themessage flow will be discussed in the context of a satellitecommunication system that includes a UT, a BxP, an AxP, and a CNCP.

With reference to FIGS. 26A and 26B, at a first operation (1), the UT isin idle mode and de-registered. In addition, a service restriction basedon distance and/or duration is ongoing.

At some point in time, the UT's RCL determines whether the servicerestriction has lapsed. For example, a restriction timer may have lapsedor the UT may have moved. If the UT is camping on a cell and the servicerestriction has lapsed, the UT uses PACdefault to initiate CNCL mobilityprocedures (block 2604). In this case, the RCL sends PACdefault to theCNCL and the CNCL initiates an Attach procedure. Otherwise, if the“forbidden paging areas for regional provision of service” list isreset, the UT may perform a cell selection to look for suitablecandidate cell/beam.

In a first operation (1), the UT uses PACdefault to initiate CNCLmobility procedures. Specifically, the UT initiates a Radio connectionby sending a Radio Connection Request including PACdefault to theBxP/AxP. Upon receiving the Radio Connection Request, at block 2606, theACP serving the UT assigns a PAC from the valid range of PACs(designated PACa in this example).

At a second operation (2), the ACP sends the assigned PAC to the UT in aRadio Connection Reject. The PAC value is maintained in UT context.

The Attach procedure is aborted due to the change in PA information(block 2608). The UT's RCL reports the failure of the connectionestablishment procedure to the UT's CNCL. The failure being indicated asresult of a cause “PA information changed.” A new Radio connection isinitiated with the assigned PAC. At a third operation (3), the UT sendsa Radio Connection Request that includes the assigned PAC.

At a fourth operation (4), the ACP sends an Initial UT Message to theCore Network Control Plane (CNCP) for a Core Network Interface logicalconnection establishment with the received Attach Request and theassigned PAC value. In a fifth operation (5) through a seventh operation(7), UT context is established between the ACP and the CNCP. CNCLSecurity is activated in the fifth operation (5). The CNCP sends anInitial Context Setup Request including an Attach Accept to the ACP inthe sixth operation (6). The Attach Accept includes the same PAC (thePAC received in the Initial UT Message). In the seventh operation (7),the ACP activates Radio Connection Layer (RCL) security.

The ACP then waits for the UT's geographic location. In an eighthoperation (8), the UT sends a Location Indication following the RCLsecurity activation. The ACP stores the received UT location information(block 2610).

The ACP determines that the UT location does not fall under anyforbidden area (block 2612). The ACP thus assigns a new PAC (PACa) forthe UT and sends the new PAC using a reconfiguration procedure. To thisend, in a ninth operation (9), the ACP sends a Radio ConnectionReconfiguration to the UT. The Radio Connection Reconfiguration includesan Attach Accept with the assigned PAC.

In a ninth operation (9), if the ACP determines that the UT locationdoes not fall under any forbidden area (block 2612), a connectionreconfiguration may be initiated setting up Radio Signaling Paths (e.g.,RSP2) and Radio Data Paths (RDPs). The Radio Connection Reconfigurationincludes an Attach Accept with the assigned PAC. The UT's CNCL gets thePAI information in the Attach Accept. The CNCL stores the received PACand compares it against the last PAC (in this case PACdefault) todetermine the next action. The CNCL may use Table 1 for this purpose asdiscussed above. In a tenth operation (10), the UT sends a RadioConnection Reconfiguration Complete to the ACP. In an eleventh operation(11), the ACP sends an Initial Context Setup Response to the CNCP.

The UT sends a Temporary Network Identifier (TNI) report before sendingan Attach Complete message (block 2614). Thus, in a twelfth operation(12), the UT sends a TNI-Report including the new TNI to the ACP. Uponreceiving this information, the ACP creates a new entry for the TNI in aPosition Database (block 2616). At a thirteenth operation (13), the UTsends an Attach Complete to the CNCP and the procedure ends.

If the UT location did fall under a forbidden area, the proceduresdiscussed above in conjunction with FIG. 20 or FIG. 23 may be followed.

IX. Detailed Examples for Efficient Connection Release

The disclosure relates in some aspects to techniques that facilitate anefficient release of a connection. In some aspects, these techniques maybe used to address Issue #4 discussed above.

Such a technique may be used for efficiently releasing a radioconnection in scenarios where a connection and bearers are establishedfor RCL-specific procedures and the UT does not have any user data tosend (e.g., a UT location report, a unicast request, a unicast response,etc.). The UT may initiate release of a Radio connection by sending anotification (via a known message or a new message) to the ACP after thecompletion of the procedure for which a signaling connection wasestablished.

IX-A. UT Requests Connection Release with Additional Parameter in LastUL Signal

FIGS. 27A and 27B illustrate a message flow diagram for a procedurewhere a UT sends a location indication message that includes a requestfor a connection release in accordance with some aspects of thedisclosure. The message flow will be discussed in the context of asatellite communication system that includes a UT, a BxP, an AxP, and aCNCP.

Initially (block 2702), the UT is attach or updated with PACa. Inaddition, default bearers (paths) are established. The UT is inConnection Management (CM) state IDLE and the CNI is released. When theUT's RCL requires a connection for sending a UT location report, aunicast request, or a unicast response, the RCL sends a new trigger tothe UT's CNCL (block 2702). The CNCL initiates a PAU Request with type‘PA Updating’ and an Active flag set as ‘1’. The message is integrityprotected as discussed herein.

In a first operation (1), the UT sends a Radio Connection Request thatincludes the assigned PAC (PACa) to the ACP. In a second operation (2),the ACP sends a Radio Connection Setup to the UT. In a third operation(3), the UT sends a Radio Connection Setup Complete with a PAU Requestto the ACP. In a fourth operation (4), the ACP sends an Initial UTMessage to the CNCP with the PAU Request and the PAC value. The CNCPdoes an integrity check on the PAU Request as discussed above. In afifth operation (5), the CNCP sends an Initial Context Setup Requestincluding a PAU Accept to the AxP. In a sixth operation (6), the ACPactivates Radio Connection Layer (RCL) security. The AxP waits for theUT's location information after activating RCL security.

In a seventh operation (7), the UT sends a Location Indication to theACP after RCL security activation. The Location Indication includes aConnection Release Indication set to TRUE, thereby indicating that theUT is to be released from the connection once the procedure for whichthe connection was established has ended.

The ACP updates a location database with the received UT locationinformation (block 2706). In addition, the ACP stores the ConnectionRelease Indication status (block 2708).

If the ACP determines that the UT location does not fall under anyforbidden area, the ACP completes the Initial Context Setup procedure.In an eighth operation (8), the ACP sends a Radio ConnectionReconfiguration with a PAU Accept to the UT. In a ninth operation (9),the UT sends a Radio Connection Reconfiguration Complete to the ACP. Ina tenth operation (10), the ACP sends an Initial Context Setup Responseto the CNCP.

If, at block 2710, the connection was established for an RCL-specificprocedure and the procedure has completed (e.g., the Connection ReleaseIndication is set as TRUE), the AxP initiates a context release requestto CNCP immediately after the tenth operation (block 2712). Accordingly,at an eleventh operation (11), the ACP sends a UT Context ReleaseRequest to the CNCP. The UT Context Release Request include a RadioNetwork Layer cause of “User Inactivity.”

Otherwise, if the connection was not established for an RCL-specificprocedure or the procedure has not completed (e.g., the ConnectionRelease Indication is not set as TRUE or was not received), the AxP maytrack user activity and when criteria for user inactivity is met, theAxP may request the CNCP to initiate a context release (block 2714).Accordingly, the ACP may wait for user inactivity (block 2716) and theninitiates a context release due to user inactivity (block 2718).Accordingly, at a twelfth operation (12), the ACP sends a UT ContextRelease Request to the CNCP, including a Radio Network Layer cause of“User Inactivity.”

The CNCP may follow up with UT Context Release Command to break Radioconnection. At a thirteenth operation (13), the CNCP sends a UT ContextRelease Command to the ACP. At a fourteenth operation (14) and afifteenth operation (15), the ACP sends a Radio Connection Release tothe UT and a UT Context Release Complete to the CNCP. The aboveoperations thus release a Radio connection when the purpose of signalingestablishment is met.

IX-B. UT Requests Connection Release with a New Radio Signal

FIGS. 28A and 28B illustrate a message flow diagram for a procedurewhere a UT requests a connection release (e.g., via a new Radio signal)with after a procedure (e.g., an RCL procedure) is over in accordancewith some aspects of the disclosure. The message flow will be discussedin the context of a satellite communication system that includes a UT, aBxP, an AxP, and a CNCP.

Initially, the UT is attach or updated with PACa (block 2802). Inaddition, default bearers (paths) are established. The UT is inConnection Management (CM) state IDLE and the CNI is released. When theUT's RCL requires a connection for sending a UT location report, aunicast request, or a unicast response, the RCL sends a new trigger tothe UT's CNCL (block 2804). The CNCL initiates a PAU Request with type‘PA Updating’ and an Active flag set as ‘1’. The message is integrityprotected as discussed herein.

In a first operation (1), the UT sends a Radio Connection Request thatincludes the assigned PAC (PACa) to the ACP. In a second operation (2),the ACP sends a Radio Connection Setup to the UT. In a third operation(3), the UT sends a Radio Connection Setup Complete with a PAU Requestto the ACP. In a fourth operation (4), the ACP sends an Initial UTMessage to the CNCP with the PAU Request and the PAC value. The CNCPdoes an integrity check on the PAU Request as discussed above. In afifth operation (5), the CNCP sends an Initial Context Setup Requestincluding a PAU Accept to the AxP. In a sixth operation (6), the ACPactivates Radio Connection Layer (RCL) security. The AxP waits for theUT's location information after activating RCL security.

In a seventh operation (7), the UT sends a Location Indication to theACP after RCL security activation. The ACP updates a location databasewith the received UT location information (block 2806).

If the ACP determines that the UT location does not fall under anyforbidden area, the ACP completes the Initial Context Setup procedure.In an eighth operation (8), the ACP sends a Radio ConnectionReconfiguration with a PAU Accept to the UT. In a ninth operation (9),the UT sends a Radio Connection Reconfiguration Complete to the ACP. Ina tenth operation (10), the ACP sends an Initial Context Setup Responseto the CNCP.

If the connection was established for an RCL-specific procedure and theprocedure has completed, the AxP proceeds to immediately release thecontext (block 2808). In this case, at an eleventh operation (11), theACP receives a Radio Connection Release Request from the UT. Inresponse, the ACP takes action to release the context immediately (block2810). Thus, at a twelfth operation (12), the ACP sends a UT ContextRelease Request to the CNCP. The UT Context Release Request include aRadio Network Layer cause of “User Inactivity.”

Otherwise, if the connection was not established for an RCL-specificprocedure or the procedure has not completed (e.g., the Radio ConnectionRelease Request was not received), the AxP may track user activity andwhen criteria for user inactivity is met, the AxP may request the CNCPto initiate a context release (block 2814). Accordingly, the ACP maywait for user inactivity (block 2816) and then initiates a contextrelease due to user inactivity (block 2818). Accordingly, at athirteenth operation (13), the ACP sends a UT Context Release Request tothe CNCP, including a Radio Network Layer cause of “User Inactivity.”

The CNCP may follow up with UT Context Release Command to break theRadio connection. At a fourteenth operation (14), the CNCP sends a UTContext Release Command to the ACP. At a fifteenth operation (15) and asixteenth operation (16), the ACP sends a Radio Connection Release tothe UT and a UT Context Release Complete to the CNCP. The aboveoperations thus release a Radio connection when the purpose of signalingestablishment is met.

X. Detailed Example for UT Location Reporting

FIG. 29 illustrates a message flow diagram for a procedure where anetwork initiates UT location reporting in accordance with some aspectsof the disclosure. In some aspects, these techniques may be used toaddress Issue #5 discussed above. The message flow will be discussed inthe context of a satellite communication system that includes a UT, aBxP, an AxP, and a CNCP.

The procedure shown in FIG. 29 can be used, for example, whenever theACP requires the UT's current GPS location. The ACP initiates theprocedure by sending a Location Request. The UT may report its latestlocation to ACP in a Location Indication message. This procedure may beused independent of threshold-based UT location reporting.

In a first operation (1), RCL security is active.

At some point in time, in a second operation (2), the AxP sends aLocation Request to the UT. For example, the AxP may run a guard timerwhereby, on expiry, the AxP sends a Location Request or a Release RadioConnection message.

In a third operation (3), the UT sends a Location Indication to the AxP.The Location Indication includes the GPS location of the UT or someother suitable indication of the UT's location. The AxP then updates alocation database with the UT's location information (block 2902).

XI. Detailed Example for Reconfiguring a Reporting Threshold

FIG. 30 illustrates a message flow diagram for a procedure where networksends a location reporting threshold to a UT in accordance with someaspects of the disclosure. In some aspects, these techniques may be usedto address Issue #6 discussed above. The message flow will be discussedin the context of a satellite communication system that includes a UT, aBxP, an AxP, and a CNCP.

Initially, the UT is in connected mode with active data bearers (block3002). In a first operation (1), the UT reports it location informationby sending a Location Indication to the ACP. This reporting is based ona Location Change Threshold defined, for example, at the time of Radioconnection setup.

Upon reception of the UT location information, the ACP updates alocation database with the location information (block 3004).

If the ACP determines that the UT location does not fall under anyforbidden area, the ACP can evaluate the UT's probability of enteringany nearby forbidden area (block 3006). If the probability issignificant, at block 3008, the ACP may recalculate one or more locationchange reporting thresholds (e.g., reduce a distance threshold and/or aduration threshold to the increase frequency of location reporting). Anynewly set restriction thresholds (Location Change Threshold) arecommunicated to UT via a Radio Connection Reconfiguration message in afirst operation (1). The UT then reports its location using the newthreshold or thresholds (block 3010). At a third operation (3), the UTsends a Radio Connection Reconfiguration Complete to the ACP.

XII. Example Apparatuses and Processes

Several examples of apparatuses and processes that may be implemented inaccordance with the teachings herein follow. It should be appreciatedthat other apparatuses and processes may be used in other examples.

First Example Apparatus

FIG. 31 illustrates a block diagram of an example hardwareimplementation of an apparatus 3100 configured to communicate accordingto one or more aspects of the disclosure. For example, the apparatus3100 could embody or be implemented within a GN, or some other type ofdevice that supports satellite communication. In variousimplementations, the apparatus 3100 could embody or be implementedwithin a gateway, a ground station, a satellite ground network, avehicular component, or any other electronic device having circuitry.

The apparatus 3100 includes a communication interface 3102 (e.g., atleast one transceiver), a storage medium 3104, a user interface 3106, amemory device (e.g., a memory circuit) 3108, and a processing circuit3110 (e.g., at least one processor). In various implementations, theuser interface 3106 may include one or more of: a keypad, a display, aspeaker, a microphone, a touchscreen display, of some other circuitryfor receiving an input from or sending an output to a user.

These components can be coupled to and/or placed in electricalcommunication with one another via a signaling bus or other suitablecomponent, represented generally by the connection lines in FIG. 31. Thesignaling bus may include any number of interconnecting buses andbridges depending on the specific application of the processing circuit3110 and the overall design constraints. The signaling bus linkstogether various circuits such that each of the communication interface3102, the storage medium 3104, the user interface 3106, and the memorydevice 3108 are coupled to and/or in electrical communication with theprocessing circuit 3110. The signaling bus may also link various othercircuits (not shown) such as timing sources, peripherals, voltageregulators, and power management circuits, which are well known in theart, and therefore, will not be described any further.

The communication interface 3102 provides a means for communicating withother apparatuses over a transmission medium. In some implementations,the communication interface 3102 includes circuitry and/or programmingadapted to facilitate the communication of information bi-directionallywith respect to one or more communication devices in a network. In someimplementations, the communication interface 3102 is adapted tofacilitate wireless communication of the apparatus 3100. In theseimplementations, the communication interface 3102 may be coupled to oneor more antennas 3112 as shown in FIG. 31 for wireless communicationwithin a wireless communication system. The communication interface 3102can be configured with one or more standalone receivers and/ortransmitters, as well as one or more transceivers. In the illustratedexample, the communication interface 3102 includes a transmitter 3114and a receiver 3116. The communication interface 3102 serves as oneexample of a means for receiving and/or means transmitting.

The memory device 3108 may represent one or more memory devices. Asindicated, the memory device 3108 may maintain paging and locationinformation 3118 along with other information used by the apparatus3100. In some implementations, the memory device 3108 and the storagemedium 3104 are implemented as a common memory component. The memorydevice 3108 may also be used for storing data that is manipulated by theprocessing circuit 3110 or some other component of the apparatus 3100.

The storage medium 3104 may represent one or more computer-readable,machine-readable, and/or processor-readable devices for storingprogramming, such as processor executable code or instructions (e.g.,software, firmware), electronic data, databases, or other digitalinformation. The storage medium 3104 may also be used for storing datathat is manipulated by the processing circuit 3110 when executingprogramming. The storage medium 3104 may be any available media that canbe accessed by a general purpose or special purpose processor, includingportable or fixed storage devices, optical storage devices, and variousother mediums capable of storing, containing or carrying programming

By way of example and not limitation, the storage medium 3104 mayinclude a magnetic storage device (e.g., hard disk, floppy disk,magnetic strip), an optical disk (e.g., a compact disc (CD) or a digitalversatile disc (DVD)), a smart card, a flash memory device (e.g., acard, a stick, or a key drive), a random access memory (RAM), a readonly memory (ROM), a programmable ROM (PROM), an erasable PROM (EPROM),an electrically erasable PROM (EEPROM), a register, a removable disk,and any other suitable medium for storing software and/or instructionsthat may be accessed and read by a computer. The storage medium 3104 maybe embodied in an article of manufacture (e.g., a computer programproduct). By way of example, a computer program product may include acomputer-readable medium in packaging materials. In view of the above,in some implementations, the storage medium 3104 may be a non-transitory(e.g., tangible) storage medium.

The storage medium 3104 may be coupled to the processing circuit 3110such that the processing circuit 3110 can read information from, andwrite information to, the storage medium 3104. That is, the storagemedium 3104 can be coupled to the processing circuit 3110 so that thestorage medium 3104 is at least accessible by the processing circuit3110, including examples where at least one storage medium is integralto the processing circuit 3110 and/or examples where at least onestorage medium is separate from the processing circuit 3110 (e.g.,resident in the apparatus 3100, external to the apparatus 3100,distributed across multiple entities, etc.).

Programming stored by the storage medium 3104, when executed by theprocessing circuit 3110, causes the processing circuit 3110 to performone or more of the various functions and/or process operations describedherein. For example, the storage medium 3104 may include operationsconfigured for regulating operations at one or more hardware blocks ofthe processing circuit 3110, as well as to utilize the communicationinterface 3102 for wireless communication utilizing their respectivecommunication protocols. In some aspects, the storage medium 3104 mayinclude computer-readable medium storing computer-executable code,including code to perform the functionality described herein.

The processing circuit 3110 is generally adapted for processing,including the execution of such programming stored on the storage medium3104. As used herein, the terms “code” or “programming” shall beconstrued broadly to include without limitation instructions,instruction sets, data, code, code segments, program code, programs,programming, subprograms, software modules, applications, softwareapplications, software packages, routines, subroutines, objects,executables, threads of execution, procedures, functions, etc., whetherreferred to as software, firmware, middleware, microcode, hardwaredescription language, or otherwise.

The processing circuit 3110 is arranged to obtain, process and/or senddata, control data access and storage, issue commands, and control otherdesired operations. The processing circuit 3110 may include circuitryconfigured to implement desired programming provided by appropriatemedia in at least one example. For example, the processing circuit 3110may be implemented as one or more processors, one or more controllers,and/or other structure configured to execute executable programmingExamples of the processing circuit 3110 may include a general purposeprocessor, a digital signal processor (DSP), an application-specificintegrated circuit (ASIC), a field programmable gate array (FPGA) orother programmable logic component, discrete gate or transistor logic,discrete hardware components, or any combination thereof designed toperform the functions described herein. A general purpose processor mayinclude a microprocessor, as well as any conventional processor,controller, microcontroller, or state machine. The processing circuit3110 may also be implemented as a combination of computing components,such as a combination of a DSP and a microprocessor, a number ofmicroprocessors, one or more microprocessors in conjunction with a DSPcore, an ASIC and a microprocessor, or any other number of varyingconfigurations. These examples of the processing circuit 3110 are forillustration and other suitable configurations within the scope of thedisclosure are also contemplated.

According to one or more aspects of the disclosure, the processingcircuit 3110 may be adapted to perform any or all of the features,processes, functions, operations and/or routines for any or all of theapparatuses described herein. For example, the processing circuit 3110may be configured to perform any of the steps, functions, and/orprocesses described with respect to FIGS. 1-30 and 32-34. As usedherein, the term “adapted” in relation to the processing circuit 3110may refer to the processing circuit 3110 being one or more ofconfigured, used, implemented, and/or programmed to perform a particularprocess, function, operation and/or routine according to variousfeatures described herein.

The processing circuit 3110 may be a specialized processor, such as anapplication-specific integrated circuit (ASIC) that serves as a meansfor (e.g., structure for) carrying out any one of the operationsdescribed in conjunction with FIGS. 1-30 and 32-34. The processingcircuit 3110 serves as one example of a means for transmitting and/or ameans for receiving. In some implementations, the processing circuit3110 incorporates the functionality of the GN controller 250 of FIG. 2.

According to at least one example of the apparatus 3100, the processingcircuit 3110 may include one or more of a circuit/module for determiningthat a UT is located in a forbidden area 3120, a circuit/module forsending 3122, a circuit/module for conducting an update procedure 3124,a circuit/module for receiving 3126, a circuit/module for determining aproximity of a UT to a forbidden area 3128, a circuit/module fordefining a location reporting threshold 3130, a circuit/module fordetermining that location information for a UT is needed 3132, acircuit/module for determining that a UT will enter idle mode 3134, or acircuit/module for determining that PAC information is to be sent 3136.

As mentioned above, programming stored by the storage medium 3104, whenexecuted by the processing circuit 3110, causes the processing circuit3110 to perform one or more of the various functions and/or processoperations described herein. For example, the programming, when executedby the processing circuit 3110, may cause the processing circuit 3110 toperform the various functions, steps, and/or processes described hereinwith respect to FIGS. 1-30 and 32-34 in various implementations. Asshown in FIG. 31, the storage medium 3104 may include one or more ofcode for determining that a UT is located in a forbidden area 3140, codefor sending 3142, code for conducting an update procedure 3144, code forreceiving 3146, code for determining a proximity of a UT to a forbiddenarea 3148, code for defining a location reporting threshold 3150, codefor determining that location information for a UT is needed 3152, codefor determining that a UT will enter idle mode 3154, or code fordetermining that PAC information is to be sent 3156.

The circuit/module for determining that a UT is located within aforbidden area 3120 may include circuitry and/or programming (e.g., codefor determining that a UT is located within a forbidden area 3140 storedon the storage medium 3104) adapted to perform several functionsrelating to, for example, determining where a UT is located relative toa particular area. In some aspects, the circuit/module for determiningthat a UT is located within a forbidden area 3120 (e.g., a means fordetermining that a UT is located within a forbidden area) may correspondto, for example, a processing circuit.

In some aspects, the circuit/module for determining that a UT is locatedwithin a forbidden area 3120 may compare a location indicated by GPScoordinates with an ellipsoid point and a distance from the ellipsoidpoint. In some aspects, the circuit/module for determining that a UT islocated within a forbidden area 3120 may perform the correspondingoperations described above in conjunction with FIGS. 8-30. In any event,the circuit/module for determining that a UT is located within aforbidden area 3120 may output a result of the determination (e.g., tothe circuit/module for sending 3122, the communication interface 3102,the memory device 3108, or some other component).

The circuit/module for sending 3122 may include circuitry and/orprogramming (e.g., code for sending 3142 stored on the storage medium3104) adapted to perform several functions relating to, for example,sending (e.g., transmitting) information. In some implementations, thecircuit/module for sending 3122 may obtain information (e.g., from thecircuit/module for determining that a UT is located within a forbiddenarea 3120, the memory device 3108, or some other component of theapparatus 3100), process the information (e.g., encode the informationfor transmission), and send the information to another component (e.g.,the transmitter 3114, the communication interface 3102, or some othercomponent) that will transmit the information to another device. In somescenarios (e.g., if the circuit/module for sending 3122 includes atransmitter), the circuit/module for sending 3122 transmits theinformation directly to another device (e.g., the ultimate destination)via radio frequency signaling or some other type of signaling suitablefor the applicable communication medium.

The circuit/module for sending 3122 (e.g., a means for sending) may takevarious forms. In some aspects, the circuit/module for sending 3122 maycorrespond to, for example, an interface (e.g., a bus interface, asend/receive interface, or some other type of signal interface), acommunication device, a transceiver, a transmitter, or some othersimilar component as discussed herein. In some implementations, thecommunication interface 3102 includes the circuit/module for sending3122 and/or the code for sending 3142. In some implementations, thecircuit/module for sending 3122 and/or the code for sending 3142 isconfigured to control the communication interface 3102 (e.g., atransceiver or a transmitter) to transmit information.

The circuit/module for conducting an update procedure 3124 may includecircuitry and/or programming (e.g., code for conducting an updateprocedure 3144 stored on the storage medium 3104) adapted to performseveral functions relating to, for example, performing updateoperations. In some aspects, the circuit/module for conducting an updateprocedure 3124 (e.g., a means for conducting an update procedure) maycorrespond to, for example, a processing circuit.

In some aspects, the circuit/module for conducting an update procedure3124 may perform a CNCL update procedure. In some aspects, thecircuit/module for conducting an update procedure 3124 may update a PAC.In some aspects, the circuit/module for conducting an update procedure3124 may perform the corresponding operations described above inconjunction with FIGS. 8-30. In any event, the circuit/module forconducting an update procedure 3124 may output a result of the procedure(e.g., to the communication interface 3102, the memory device 3108, orsome other component).

The circuit/module for receiving 3126 may include circuitry and/orprogramming (e.g., code for receiving 3146 stored on the storage medium3104) adapted to perform several functions relating to, for example,receiving information. In some scenarios, the circuit/module forreceiving 3126 may obtain information (e.g., from the communicationinterface 3102, the memory device, or some other component of theapparatus 3100) and processes (e.g., decodes) the information. In somescenarios (e.g., if the circuit/module for receiving 3126 is or includesan RF receiver), the circuit/module for receiving 3126 may receiveinformation directly from a device that transmitted the information. Ineither case, the circuit/module for receiving 3126 may output theobtained information to another component of the apparatus 3100 (e.g.,the memory device 3108, or some other component).

The circuit/module for receiving 3126 (e.g., a means for receiving) maytake various forms. In some aspects, the circuit/module for receiving3126 may correspond to, for example, an interface (e.g., a businterface, a send/receive interface, or some other type of signalinterface), a communication device, a transceiver, a receiver, or someother similar component as discussed herein. In some implementations,the communication interface 3102 includes the circuit/module forreceiving 3126 and/or the code for receiving 3146. In someimplementations, the circuit/module for receiving 3126 and/or the codefor receiving 3146 is configured to control the communication interface3102 (e.g., a transceiver or a receiver) to receive information.

The circuit/module for determining a proximity of a UT to a forbiddenarea 3128 may include circuitry and/or programming (e.g., code fordetermining a proximity of a UT to a forbidden area 3148 stored on thestorage medium 3104) adapted to perform several functions relating to,for example, determining how close a UT is to a particular area. In someaspects, the circuit/module for determining that a UT is located withina forbidden area 3120 (e.g., a means for determining a proximity of a UTto a forbidden area) may correspond to, for example, a processingcircuit.

In some aspects, the circuit/module for determining a proximity of a UTto a forbidden area 3128 may compare a location (or locations) indicatedby GPS coordinates with an ellipsoid point and a distance from theellipsoid point. In some aspects, the circuit/module for determining aproximity of a UT to a forbidden area 3128 may perform the correspondingoperations described above in conjunction with FIGS. 8-30. In any event,the circuit/module for determining a proximity of a UT to a forbiddenarea 3128 may output a result of the determination (e.g., to thecircuit/module for sending 3122, the communication interface 3102, thememory device 3108, or some other component).

The circuit/module for defining a location reporting threshold 3130 mayinclude circuitry and/or programming (e.g., code for defining a locationreporting threshold 3150 stored on the storage medium 3104) adapted toperform several functions relating to, for example, specifying at leastone threshold. In some aspects, the circuit/module for defining alocation reporting threshold 3130 (e.g., a means for defining a locationreporting threshold) may correspond to, for example, a processingcircuit.

In some aspects, the circuit/module for defining a location reportingthreshold 3130 may decrease a threshold (e.g., to invoke more frequentreports) the closer a UT gets to a particular area (e.g., a forbiddenarea). In some aspects, the circuit/module for defining a locationreporting threshold 3130 may perform the corresponding operationsdescribed above in conjunction with FIGS. 8-30. In any event, thecircuit/module for defining a location reporting threshold 3130 mayoutput a result of the definition (e.g., to the circuit/module forsending 3122, the communication interface 3102, the memory device 3108,or some other component).

The circuit/module for determining that location information for a UT isneeded 3132 may include circuitry and/or programming (e.g., code fordetermining that location information for a UT is needed 3152 stored onthe storage medium 3104) adapted to perform several functions relatingto, for example, determining whether to obtain location information. Insome aspects, the circuit/module for determining that locationinformation for a UT is needed 3132 (e.g., a means for determining thatlocation information for a UT is needed) may correspond to, for example,a processing circuit.

In some aspects, the circuit/module for determining that locationinformation for a UT is needed 3132 may trigger a request for locationinformation upon expiry of a guard timer. In some aspects, thecircuit/module for determining that location information for a UT isneeded 3132 may perform the corresponding operations described above inconjunction with FIGS. 8-30. In any event, the circuit/module fordetermining that location information for a UT is needed 3132 may outputa result of the determination (e.g., to the circuit/module for sending3122, the communication interface 3102, the memory device 3108, or someother component).

The circuit/module for determining that a UT will enter idle mode 3134may include circuitry and/or programming (e.g., code for determiningthat a UT will enter idle mode 3154 stored on the storage medium 3104)adapted to perform several functions relating to, for example,determining an operating mode of a UT. In some aspects, thecircuit/module for determining that a UT will enter idle mode 3134(e.g., a means for determining that a UT will enter idle mode) maycorrespond to, for example, a processing circuit.

In some aspects, the circuit/module for determining that a UT will enteridle mode 3134 may involving receiving a corresponding indication fromthe UT and triggering an action (e.g., a connection release) based onthe indication. In some aspects, the circuit/module for determining thata UT will enter idle mode 3134 may perform the corresponding operationsdescribed above in conjunction with FIGS. 8-30. In any event, thecircuit/module for determining that a UT will enter idle mode 3134 mayoutput a result of the determination (e.g., to the circuit/module forsending 3122, the communication interface 3102, the memory device 3108,or some other component).

The circuit/module for determining that PAC information is to be sent3136 may include circuitry and/or programming (e.g., code fordetermining that PAC information is to be sent 3156 stored on thestorage medium 3104) adapted to perform several functions relating to,for example, determining whether to send information. In some aspects,the circuit/module for determining that PAC information is to be sent3136 (e.g., a means for determining that PAC information is to be sent)may correspond to, for example, a processing circuit.

In some aspects, the circuit/module for determining that PAC informationis to be sent 3136 may involving determining that a UT has beenhanded-off and determining that the UT needs new PAC information due tothe hand-off. In some aspects, the circuit/module for determining thatPAC information is to be sent 3136 may perform the correspondingoperations described above in conjunction with FIGS. 8-30. In any event,the circuit/module for determining that PAC information is to be sent3136 may output a result of the determination (e.g., to thecircuit/module for sending 3122, the communication interface 3102, thememory device 3108, or some other component).

First Example Process

FIG. 32 illustrates a process 3200 for communication in accordance withsome aspects of the disclosure. The process 3200 may take place within aprocessing circuit (e.g., the processing circuit 3110 of FIG. 31), whichmay be located in a GN or some other suitable apparatus. Of course, invarious aspects within the scope of the disclosure, the process 3200 maybe implemented by any suitable apparatus capable of supportingcommunication-related operations.

At block 3202, an apparatus (e.g., a GN) determines that a user terminal(UT) is located within a forbidden area. For example, a GN may comparethe UT's current location (e.g., in GPS coordinates) with the knownboundaries of a forbidden area (e.g., also defined in GPS coordinates).

At block 3204, the apparatus sends a Radio Connection Reconfigurationmessage to the UT as a result of the determination of block 3202. Insome aspects, the Radio Connection Reconfiguration message may include apaging area code associated with the forbidden area for the UT.

At optional block 3206, the apparatus may send a Radio ConnectionRelease message after sending the Radio Connection Reconfigurationmessage at block 3204. In some aspects, the Radio Connection Releasemessage may include a request to initiate (e g, immediately initiate) aCore Network Control Layer update procedure In some aspects, the RadioConnection Release message may include timing information that controlswhen the UT is to attempt reconfiguration. In some aspects, the RadioConnection Release message may include information indicative of theforbidden area. In some aspects, the information indicative of theforbidden area may include an ellipsoid point (e.g., GPS coordinates ofthe center of the ellipsoid) and a distance from the ellipsoid pointthat together indicate (e.g., approximate) a forbidden area. In someaspects, the information indicative of the forbidden area may include anellipsoid point (e.g., a center point) and a distance (e.g., a radius)from the ellipsoid point that together indicate (e.g., approximate) aforbidden area.

At optional block 3208, the apparatus may conduct a Core Network ControlLayer update procedure as a result of sending the Radio ConnectionRelease message. In some aspects, the Core Network Control Layer updateprocedure may include sending a forbidden paging area code (PAC).

Second Example Process

FIG. 33 illustrates a process 3300 for communication in accordance withsome aspects of the disclosure. The process 3300 may take place within aprocessing circuit (e.g., the processing circuit 3110 of FIG. 31), whichmay be located in a GN or some other suitable apparatus. Of course, invarious aspects within the scope of the disclosure, the process 3300 maybe implemented by any suitable apparatus capable of supportingcommunication-related operations.

At block 3302, an apparatus (e.g., a GN) receives location informationfor a user terminal (UT).

At block 3304, the apparatus determines, based on the locationinformation, a proximity of the UT to a forbidden area. In some aspects,the determination may include determining that the UT is near theforbidden area. In some aspects, the determination may includedetermining that the UT is in (is located within) the forbidden area.

At block 3306, the apparatus defines a location reporting threshold forthe UT based on the determination of block 3304. For example, thethreshold may indicate a distance (e.g., from the center of therestricted area) within which service for the UT is restricted. In someaspects, the location reporting threshold may include (e.g., may be) adistance threshold. In some aspects, the location reporting thresholdmay include a duration threshold. For example, the threshold mayindicate an amount of time that service for the UT is restricted.

At optional block 3308, the apparatus may send the location reportingthreshold to the UT (e.g., via a Radio Connection Reconfigurationmessage).

Third Example Process

FIG. 34 illustrates a process 3400 for communication in accordance withsome aspects of the disclosure. The process 3400 may take place within aprocessing circuit (e.g., the processing circuit 3110 of FIG. 31), whichmay be located in a GN or some other suitable apparatus. Of course, invarious aspects within the scope of the disclosure, the process 3400 maybe implemented by any suitable apparatus capable of supportingcommunication-related operations.

At block 3402, an apparatus (e.g., a GN) determines that locationinformation for a user terminal (UT) is needed. For example, a GN mayrepeatedly (e.g., based on a timer) update a location database thatincludes information about the last known location of one or more UTs.

At block 3404, the apparatus sends a request for the locationinformation as a result of the determination of block 3402.

At optional block 3406, the apparatus may receive the locationinformation from the user terminal (e.g., in response to the request ofblock 3404).

At optional block 3408, the apparatus may determine that the user islocated within a forbidden area. In some aspects, this determination maybe based on the location information received at block 3406.

Second Example Apparatus

FIG. 35 illustrates a block diagram of an example hardwareimplementation of another apparatus 3500 configured to communicateaccording to one or more aspects of the disclosure. For example, theapparatus 3500 could embody or be implemented within a UT or some othertype of device that supports satellite communication. In variousimplementations, the apparatus 3500 could embody or be implementedwithin a vehicular component, or any other electronic device havingcircuitry.

The apparatus 3500 includes a communication interface (e.g., at leastone transceiver) 3502, a storage medium 3504, a user interface 3506, amemory device 3508 (e.g., storing paging and location information 3518),and a processing circuit (e.g., at least one processor) 3510. In variousimplementations, the user interface 3506 may include one or more of: akeypad, a display, a speaker, a microphone, a touchscreen display, ofsome other circuitry for receiving an input from or sending an output toa user. The communication interface 3502 may be coupled to one or moreantennas 3512, and may include a transmitter 3514 and a receiver 3516.In general, the components of FIG. 35 may be similar to correspondingcomponents of the apparatus 3100 of FIG. 31.

According to one or more aspects of the disclosure, the processingcircuit 3510 may be adapted to perform any or all of the features,processes, functions, operations and/or routines for any or all of theapparatuses described herein. For example, the processing circuit 3510may be configured to perform any of the steps, functions, and/orprocesses described with respect to FIGS. 1-30 and 36-42. As usedherein, the term “adapted” in relation to the processing circuit 3510may refer to the processing circuit 3510 being one or more ofconfigured, used, implemented, and/or programmed to perform a particularprocess, function, operation and/or routine according to variousfeatures described herein.

The processing circuit 3510 may be a specialized processor, such as anapplication-specific integrated circuit (ASIC) that serves as a meansfor (e.g., structure for) carrying out any one of the operationsdescribed in conjunction with FIGS. 1-30 and 36-42. The processingcircuit 3510 serves as one example of a means for transmitting and/or ameans for receiving. In various implementations, the processing circuit3510 may incorporate the functionality of the control processor 420 ofFIG. 4.

According to at least one example of the apparatus 3500, the processingcircuit 3510 may include one or more of a circuit/module for determiningthat a service restriction has ended 3520, a circuit/module forconducting 3522, a circuit/module for determining that a triggercondition has occurred 3524, a circuit/module for sending 3526, acircuit/module for determining that a UT is to be assigned PAinformation 3528, a circuit/module for receiving 3530, a circuit/modulefor initiating a radio connection 3532, or a circuit/module forinitiating an update procedure 3534.

As mentioned above, programming stored by the storage medium 3504, whenexecuted by the processing circuit 3510, causes the processing circuit3510 to perform one or more of the various functions and/or processoperations described herein. For example, the programming, when executedby the processing circuit 3510, may cause the processing circuit 3510 toperform the various functions, steps, and/or processes described hereinwith respect to FIGS. 1-30 and 36-42 in various implementations. Asshown in FIG. 35, the storage medium 3504 may include one or more ofcode for determining that a service restriction has ended 3540, code forconducting 3542, code for determining that a trigger condition hasoccurred 3544, code for sending 3546, code for determining that a UT isto be assigned PA information 3548, code for receiving 3550, code forinitiating a radio connection 3552, or code for initiating an updateprocedure 3554.

The circuit/module for determining that a service restriction has ended3520 may include circuitry and/or programming (e.g., code fordetermining that a service restriction has ended 3540 stored on thestorage medium 3504) adapted to perform several functions relating to,for example, determining whether a service restriction applies. In someaspects, the circuit/module for determining that a service restrictionhas ended 3520 (e.g., a means for determining that a service restrictionhas ended) may correspond to, for example, a processing circuit.

In some aspects, the circuit/module for determining that a servicerestriction has ended 3520 may compare a the current time with athreshold or monitor the value of a timer. In some aspects, thecircuit/module for determining that a service restriction has ended 3520may compare a location indicated by GPS coordinates with an ellipsoidpoint and a distance from the ellipsoid point. In some aspects, thecircuit/module for In some aspects, the circuit/module for determiningthat a service restriction has ended 3520 may compare a locationindicated by GPS coordinates with an ellipsoid point and a distance fromthe ellipsoid point. 3520 may perform the corresponding operationsdescribed above in conjunction with FIGS. 8-30. In any event, thecircuit/module for In some aspects, the circuit/module for determiningthat a service restriction has ended 3520 may compare a locationindicated by GPS coordinates with an ellipsoid point and a distance fromthe ellipsoid point. 3520 may output a result of the determination(e.g., to the circuit/module for sending 3522, the communicationinterface 3502, the memory device 3508, or some other component).

The circuit/module for conducting 3522 may include circuitry and/orprogramming (e.g., code for conducting 3542 stored on the storage medium3504) adapted to perform several functions relating to, for example,conducting specified operations. In some aspects, the circuit/module forconducting 3522 (e.g., a means for conducting) may correspond to, forexample, a processing circuit.

In some aspects, the circuit/module for conducting 3522 may conduct atleast one mobility operation (e.g., by initiating a Radio Connection).In some aspects, the circuit/module for conducting 3522 may perform thecorresponding operations described above in conjunction with FIGS. 8-30.In any event, the circuit/module for conducting 3522 may output a resultof the procedure (e.g., to the communication interface 3502, the memorydevice 3508, or some other component).

The circuit/module for determining that a trigger condition has occurred3524 may include circuitry and/or programming (e.g., code fordetermining that a trigger condition has occurred 3544 stored on thestorage medium 3504) adapted to perform several functions relating to,for example, monitoring the status of a trigger condition. In someaspects, the circuit/module for determining that a trigger condition hasoccurred 3524 (e.g., a means for determining that a trigger conditionhas occurred) may correspond to, for example, a processing circuit.

In some aspects, the circuit/module for determining that a triggercondition has occurred 3524 may involving monitoring operations of a UTand/or a network. In some aspects, the circuit/module for determiningthat a trigger condition has occurred 3524 may perform the correspondingoperations described above in conjunction with FIGS. 8-30. In any event,the circuit/module for determining that a trigger condition has occurred3524 may output a result of the determination (e.g., to thecircuit/module for sending 3522, the communication interface 3502, thememory device 3508, or some other component).

The circuit/module for sending 3526 may include circuitry and/orprogramming (e.g., code for sending 3546 stored on the storage medium3504) adapted to perform several functions relating to, for example,sending (e.g., transmitting) information. In some implementations, thecircuit/module for sending 3526 may obtain information (e.g., from thememory device 3508, or some other component of the apparatus 3500),process the information (e.g., encode the information for transmission),and send the information to another component (e.g., the transmitter3514, the communication interface 3502, or some other component) thatwill transmit the information to another device. In some scenarios(e.g., if the circuit/module for sending 3526 includes a transmitter),the circuit/module for sending 3526 transmits the information directlyto another device (e.g., the ultimate destination) via radio frequencysignaling or some other type of signaling suitable for the applicablecommunication medium.

The circuit/module for sending 3526 (e.g., a means for sending) may takevarious forms. In some aspects, the circuit/module for sending 3526 maycorrespond to, for example, an interface (e.g., a bus interface, asend/receive interface, or some other type of signal interface), acommunication device, a transceiver, a transmitter, or some othersimilar component as discussed herein. In some implementations, thecommunication interface 3502 includes the circuit/module for sending3526 and/or the code for sending 3546. In some implementations, thecircuit/module for sending 3526 and/or the code for sending 3546 isconfigured to control the communication interface 3502 (e.g., atransceiver or a transmitter) to transmit information.

The circuit/module for determining that a UT is to be assigned PACinformation 3528 may include circuitry and/or programming (e.g., codefor determining that a UT is to be assigned PAC information 3548 storedon the storage medium 3504) adapted to perform several functionsrelating to, for example, determining whether to assign information. Insome aspects, the circuit/module for determining that a UT is to beassigned PAC information 3528 (e.g., a means for determining that a UTis to be assigned PAC information) may correspond to, for example, aprocessing circuit.

In some aspects, the circuit/module for determining that a UT is to beassigned PAC information 3528 may involving determining that a UT doesnot have valid PAC information. In some aspects, the circuit/module fordetermining that a UT is to be assigned PAC information 3528 may performthe corresponding operations described above in conjunction with FIGS.8-30. In any event, the circuit/module for determining that a UT is tobe assigned PAC information 3528 may output a result of thedetermination (e.g., to the circuit/module for sending 3522, thecommunication interface 3502, the memory device 3508, or some othercomponent).

The circuit/module for receiving 3530 may include circuitry and/orprogramming (e.g., code for receiving 3550 stored on the storage medium3504) adapted to perform several functions relating to, for example,receiving information. In some scenarios, the circuit/module forreceiving 3530 may obtain information (e.g., from the communicationinterface 3502, the memory device, or some other component of theapparatus 3500) and processes (e.g., decodes) the information. In somescenarios (e.g., if the circuit/module for receiving 3530 is or includesan RF receiver), the circuit/module for receiving 3530 may receiveinformation directly from a device that transmitted the information. Ineither case, the circuit/module for receiving 3530 may output theobtained information to another component of the apparatus 3500 (e.g.,the memory device 3508, or some other component).

The circuit/module for receiving 3530 (e.g., a means for receiving) maytake various forms. In some aspects, the circuit/module for receiving3530 may correspond to, for example, an interface (e.g., a businterface, a send/receive interface, or some other type of signalinterface), a communication device, a transceiver, a receiver, or someother similar component as discussed herein. In some implementations,the communication interface 3502 includes the circuit/module forreceiving 3530 and/or the code for receiving 3550. In someimplementations, the circuit/module for receiving 3530 and/or the codefor receiving 3550 is configured to control the communication interface3502 (e.g., a transceiver or a receiver) to receive information.

The circuit/module for initiating a radio connection 3532 may includecircuitry and/or programming (e.g., code for initiating a radioconnection 3552 stored on the storage medium 3504) adapted to performseveral functions relating to, for example, initiating radio-basedcommunication. In some aspects, the circuit/module for initiating aradio connection 3532 (e.g., a means for initiating a radio connection)may correspond to, for example, a processing circuit.

In some aspects, the circuit/module for initiating a radio connection3532 may send a Radio Connection Request and handle associatedprocessing and messages. In some aspects, the circuit/module forinitiating a radio connection 3532 may perform the correspondingoperations described above in conjunction with FIGS. 8-30. In any event,the circuit/module for initiating a radio connection 3532 may output aresult of the initiation (e.g., to the communication interface 3502, thememory device 3508, or some other component).

The circuit/module for initiating an update procedure 3534 may includecircuitry and/or programming (e.g., code for initiating an updateprocedure 3554 stored on the storage medium 3504) adapted to performseveral functions relating to, for example, initiating a specifiedprocedure. In some aspects, the circuit/module for initiating an updateprocedure 3534 (e.g., a means for initiating an update procedure) maycorrespond to, for example, a processing circuit.

In some aspects, the circuit/module for initiating an update procedure3534 may initiate a PAC update. In some aspects, the circuit/module forinitiating an update procedure 3534 may perform the correspondingoperations described above in conjunction with FIGS. 8-30. In any event,the circuit/module for initiating an update procedure 3534 may output aresult of the initiation (e.g., to the communication interface 3502, thememory device 3508, or some other component).

Fourth Example Process

FIG. 36 illustrates a process 3600 for communication in accordance withsome aspects of the disclosure. The process 3600 may take place within aprocessing circuit (e.g., the processing circuit 3510 of FIG. 35), whichmay be located in a UT, UE, or some other suitable apparatus. Of course,in various aspects within the scope of the disclosure, the process 3600may be implemented by any suitable apparatus capable of supportingcommunication-related operations.

At block 3602, an apparatus (e.g., a UT) determines that a servicerestriction for a user terminal (UT) has ended (e.g., no longerapplies). In some aspects, the service restriction may be associatedwith a forbidden area. For example, a UT may determine that that athreshold time associated with the service restriction for a restrictedarea has expired or that the UT has moved a threshold distance (e.g.,away from a center of a restricted area).

At block 3604, the apparatus conducts a mobility operation using adefault paging area code (PAC) as a result of the determination of block3602. In some aspects, the conducting of the mobility operation mayinclude initiating a Radio Connection (e.g., after initiating a Registerprocedure). In some aspects, the conducting of the mobility operationmay include initiating a Radio Connection without sending any PACinformation for the initiation of the Radio Connection. In some aspects,the default paging area code is excluded from a set of paging area codesused for paging area update operations. In some aspects, the defaultpaging area code is used between a Core Network Control Layer and aRadio Connection Layer internal to a user terminal (UT). In someaspects, the default paging area code might not be sent in any signalingmessages over-the-air.

Fifth Example Process

FIG. 37 illustrates a process 3700 for communication in accordance withsome aspects of the disclosure. The process 3700 may take place within aprocessing circuit (e.g., the processing circuit 3510 of FIG. 35), whichmay be located in a UT, UE, or some other suitable apparatus. Of course,in various aspects within the scope of the disclosure, the process 3700may be implemented by any suitable apparatus capable of supportingcommunication-related operations.

At block 3702, an apparatus (e.g., a UT) determines that a triggercondition has occurred at a user terminal (UT). In some aspects, thedetermination that the trigger condition has occurred may includedetermining that a network has completed downloading of satellitetransition information (e.g., a table that indicates satellite beam orcell availability). In some aspects, the determination that the triggercondition has occurred may include determining that the UT has completedsending of location information. In some aspects, the determination thatthe trigger condition has occurred may include determining that the UTwill transition (or has transitioned) to idle mode. In some aspects, thedetermination that the trigger condition has occurred may includedetermining that a procedure for which the connection was establishedhas completed. In some aspects, the connection is a Radio Connection forthe UT. In some aspects, the connection is a Core Network Interfaceconnection.

At block 3704, the apparatus sends a request, from the UT, to release aconnection as a result of the determination of block 3702. In someaspects, the determination that the trigger condition has occurred mayinclude determining that a user terminal (UT) will enter (or hasentered) idle mode after reporting location information for the UT.

At optional block 3706, the apparatus may send location information forthe UT. In some aspects, the location information may be sent inconjunction with the request to release the connection sent at block3704.

Sixth Example Process

FIG. 38 illustrates a process 3800 for communication in accordance withsome aspects of the disclosure. The process 3800 may take place within aprocessing circuit (e.g., the processing circuit 3510 of FIG. 35), whichmay be located in a UT, UE, or some other suitable apparatus. Of course,in various aspects within the scope of the disclosure, the process 3800may be implemented by any suitable apparatus capable of supportingcommunication-related operations.

At block 3802, an apparatus (e.g., a UT) determines that a user terminalin idle mode is to be assigned paging area code (PAC) information. Forexample, a UT may determine that it has not been assigned current PACinformation.

At block 3804, the apparatus conducts a mobility operation using adefault PAC as a result of the determination. In some aspects,conducting of the mobility operation may include initiating a RadioConnection (e.g., after initiating a Register procedure) without sendingany PAC information for the initiation of the Radio Connection. In someaspects, the default paging area code may be excluded from a set ofpaging area codes used for paging area update operations. In someaspects, the default paging area code may be used between a Core NetworkControl Layer and a Radio Connection Layer internal to a user terminal(UT). In some aspects, the default paging area code might not be sent inany signaling messages over-the-air.

Seventh Example Process

FIG. 39 illustrates a process 3900 for communication in accordance withsome aspects of the disclosure. The process 3900 may take place within aprocessing circuit (e.g., the processing circuit 3510 of FIG. 35), whichmay be located in a UT, UE, or some other suitable apparatus. Of course,in various aspects within the scope of the disclosure, the process 3900may be implemented by any suitable apparatus capable of supportingcommunication-related operations. In some aspects, the operations of theprocess 3900 may correspond, at least in part, to the operations ofFIGS. 14A-17B.

At block 3902, an apparatus (e.g., a UT) initiates a Radio Connection.In some aspects, the initiation of the Radio Connection may includesending old PAC information. In some aspects, the initiation of theRadio Connection may include sending a PAC associated with a forbiddenpaging area (PA). In some aspects, the initiation of the RadioConnection may be triggered by the receipt of the request.

At block 3904, the apparatus receives a Radio Connection reject messageafter the initiating of the Radio Connection at block 3902. In someaspects, the Radio Connection Reject message may include paging areacode (PAC) information (e.g., a newly assigned PAC). In some aspects,the Radio Connection Reject message may include timing information thatcontrols when the UT can attempt a reconnection. In some aspects, theRadio Connection Reject message may include a request for the UT to sendold PAC information in a Radio Connection Request message.

At optional block 3906, the apparatus may receive a request to updatePAC information. In some aspects, initiating of another Radio Connection(e.g., sending of a Connection Request message) may be triggered by thereceipt of the request.

At optional block 3908, the apparatus may receive a Radio ConnectionRelease message that includes timing information that controls when auser terminal (UT) is to attempt a re-connection.

At optional block 3910, the apparatus may receive a Radio ConnectionRelease message that includes information indicative of a forbiddenarea. In some aspects, the information indicative of the forbidden areamay include an ellipsoid point and a distance from the ellipsoid point.Accordingly, in some aspects, the Radio Connection Release message mayidentify an ellipsoid point and a distance from the ellipsoid pointindicative of a forbidden area.

Eighth Example Process

FIG. 40 illustrates a process 4000 for communication in accordance withsome aspects of the disclosure. The process 4000 may take place within aprocessing circuit (e.g., the processing circuit 3510 of FIG. 35), whichmay be located in a UT, UE, or some other suitable apparatus. Of course,in various aspects within the scope of the disclosure, the process 4000may be implemented by any suitable apparatus capable of supportingcommunication-related operations. In some aspects, the operations of theprocess 4000 may correspond, at least in part, to the operations ofFIGS. 14A-17B.

At block 4002, an apparatus (e.g., a UT) initiates a Radio Connection.In some aspects, the initiation of the Radio Connection may includesending old PAC information. In some aspects, the initiation of theRadio Connection may include sending a PAC associated with a forbiddenpaging area (PA). In some aspects, the initiation of the RadioConnection may be triggered by receipt of a request.

At block 4004, the apparatus receives a Radio Connection Reject messageafter the initiating of the Radio Connection at block 4002. In someaspects, the Radio Connection Reject message may include an indicationthat the UT is to immediately attempt a reconnection. For example, theRadio Connection Reject message may include a waittime parameter with avalue of zero.

At optional block 4006, the apparatus may receive a request to updatePAC information. In some aspects, initiating of another Radio Connection(e.g., sending of a Connection Request message) may be triggered by thereceipt of the request.

At optional block 4008, the apparatus may receive a Radio ConnectionRelease message that includes timing information that controls when auser terminal (UT) is to attempt a re-connection.

At optional block 4010, the apparatus may receive a Radio ConnectionRelease message that includes information indicative of a forbiddenarea. In some aspects, the information indicative of the forbidden areamay include an ellipsoid point and a distance from the ellipsoid point.Accordingly, in some aspects, the Radio Connection Release message mayidentify an ellipsoid point and a distance from the ellipsoid pointindicative of a forbidden area.

Ninth Example Process

FIG. 41 illustrates a process 4100 for communication in accordance withsome aspects of the disclosure. The process 4100 may take place within aprocessing circuit (e.g., the processing circuit 3510 of FIG. 35), whichmay be located in a UT, UE, or some other suitable apparatus. Of course,in various aspects within the scope of the disclosure, the process 4100may be implemented by any suitable apparatus capable of supportingcommunication-related operations. In some aspects, the operations of theprocess 4100 may correspond, at least in part, to the operations ofFIGS. 17A and 17B.

At block 4102, an apparatus (e.g., a UT) initiates a Radio Connection.In some aspects, the initiation of the Radio Connection may includesending current PAC information. In some aspects, the initiation of theRadio Connection may include sending old PAC information. In someaspects, the initiation of the Radio Connection includes sending a PACassociated with a forbidden paging area (PA). In some aspects, theinitiation of the Radio Connection may be triggered by the receipt ofthe request.

At block 4104, the apparatus receives a Radio Connection Reject messageafter the initiating of the Radio Connection at block 4102. In someaspects, Radio Connection Reject message may include a request for a UTto send old PAC information previously used by the UT. In some aspects,the request may be for the UT to send the old PAC information in a RadioConnection Request message.

At optional block 4106, the apparatus (e.g., a UT) may receive a requestto update PAC information. In some aspects, the request indicates tosend the old PAC information in a Radio Connection Request message. Insome aspects, initiating of another Radio Connection (e.g., sending of aConnection Request message that includes the old PAC information) istriggered by receipt of the request to update paging area codeinformation.

At optional block 4108, the apparatus may receive a Radio ConnectionRelease message that includes timing information that controls when auser terminal (UT) is to attempt a re-connection.

At optional block 4110, the apparatus may receive a Radio ConnectionRelease message that includes information indicative of a forbiddenarea. In some aspects, the information indicative of the forbidden areamay include an ellipsoid point and a distance from the ellipsoid point.Accordingly, in some aspects, the Radio Connection Release message mayidentify an ellipsoid point and a distance from the ellipsoid pointindicative of a forbidden area.

Tenth Example Process

FIG. 42 illustrates a process 4200 for communication in accordance withsome aspects of the disclosure. The process 4200 may take place within aprocessing circuit (e.g., the processing circuit 3510 of FIG. 35), whichmay be located in a UT, UE, or some other suitable apparatus. Of course,in various aspects within the scope of the disclosure, the process 4200may be implemented by any suitable apparatus capable of supportingcommunication-related operations. In some aspects, the operations of theprocess 4200 may correspond, at least in part, to the operations of FIG.16.

At block 4202, the apparatus initiates a paging area update (PAU)procedure. In some aspects, the operations of block 4204 may beperformed after conducting a mobility operation (e.g., as discussed atblock 3804 of FIG. 38).

At block 4204, the apparatus sends a message comprising an old PACpreviously used by a UT. In some aspects, the operations of block 4204may be performed after initiating the PAU procedure at block 4202. Insome aspects, the message may further include a new PAC.

At optional block 4206, an apparatus (e.g., a UT) may initiate a RadioConnection in conjunction with sending the message of block 4204. Forexample, the message may be a Connection Request message.

XIII. Other Aspects

The disclosure relates in some aspects to managing paging areainformation for a user terminal (UT) and connection signaling. In someaspects, paging area information is provided for an idle UT by defininga default paging area code (PAC) that is known by the network and theUT. In some aspects, paging area information is communicated viaconnection signaling. In some aspects, connection signaling may be usedto force a UT to invoke an update procedure (e.g., a reconnection).

The disclosure relates in some aspects to forbidden area procedures andconnection release management for a user terminal (UT). Forbiddenarea-related procedures include, for example, using a special pagingarea code (PAC) in conjunction with a forbidden area, defining alocation reporting threshold for a UT based on the proximity of the UTto a forbidden area, or using a default paging area code if a servicerestriction for a UT has ended. Connection release management includes,for example, a UT sending a request to cause the release of a RadioConnection that the UT no longer needs, or a UT sending a LocationIndication (e.g., including a flag requesting release of a connection)to release the connection used for location reporting when a UT is donesending the location information and is going to go back to idle mode.

In some aspects, a method of communication includes determining that auser terminal in idle mode is to be assigned paging area code (PAC)information, and conducting a mobility operation using a default PAC asa result of the determination. In some aspects, the conducting of themobility operation includes initiating a Register procedure, andinitiating a Radio Connection without sending any PAC information. Insome aspects, the default PAC is excluded from a set of PACs used forpaging area update operations. In some aspects, the default PAC is usedbetween a Core Network Control Layer and a Radio Connection Layerinternal to a user terminal (UT). In some aspects, the default PAC isnot sent in any signaling messages over-the-air.

In an aspect of the disclosure, an apparatus for communication includesa memory and a processor coupled to the memory. The processor and thememory are configured to determine that a user terminal in idle mode isto be assigned paging area code (PAC) information, and conduct amobility operation using a default PAC as a result of the determination.

In an aspect of the disclosure, an apparatus for communication includesmeans for determining that a user terminal in idle mode is to beassigned paging area code (PAC) information, and means for conducting amobility operation using a default PAC as a result of the determination.

In an aspect of the disclosure, a non-transitory computer-readablemedium storing computer-executable code includes code to: determine thata user terminal in idle mode is to be assigned paging area code (PAC)information, and conduct a mobility operation using a default PAC as aresult of the determination.

In some aspects, a method of communication includes initiating a RadioConnection, and receiving a Radio Connection Reject message comprisingpaging area code (PAC) information after the initiating of the RadioConnection. In some aspects, the Radio Connection Reject messageincludes timing information that controls when the UT can attempt areconnection. In some aspects, the Radio Connection Reject messageincludes a request for the UT to send old PAC information in a RadioConnection Request message. In some aspects, the initiating of the RadioConnection includes sending old PAC information. In some aspects, theinitiating of the Radio Connection comprises sending a PAC associatedwith a forbidden paging area (PA). In some aspects, the method furtherincludes receiving a request to update PAC information, wherein theinitiating of the Radio Connection is triggered by the receipt of therequest. In some aspects, the method further includes receiving a RadioConnection Release message that comprises timing information thatcontrols when a user terminal (UT) is to attempt a re-connection. Insome aspects, the method further includes receiving a Radio ConnectionRelease message that includes information indicative of a forbidden area(e.g., a forbidden zone).

In an aspect of the disclosure, an apparatus for communication includesa memory and a processor coupled to the memory. The processor and thememory are configured to initiate a Radio Connection, and receive aRadio Connection Reject message comprising paging area code (PAC)information after the initiating of the Radio Connection.

In an aspect of the disclosure, an apparatus for communication includesmeans for initiating a Radio Connection, and means for receiving a RadioConnection Reject message comprising paging area code (PAC) informationafter the initiating of the Radio Connection.

In an aspect of the disclosure, a non-transitory computer-readablemedium storing computer-executable code includes code to: initiate aRadio Connection, and receive a Radio Connection Reject messagecomprising paging area code (PAC) information after the initiating ofthe Radio Connection.

In some aspects, a method of communication includes initiating a RadioConnection, and receiving a Radio Connection Reject message after theinitiating of the Radio Connection, where the Radio Connection Rejectmessage includes an indication that a user terminal (UT) is toimmediately attempt a reconnection. In some aspects, the initiating ofthe Radio Connection includes sending old paging area code (PAC)information. In some aspects, the initiating of the Radio Connectionincludes sending a PAC associated with a forbidden paging area (PA). Insome aspects, the method further includes receiving a request to updatePAC information, wherein the initiating of the Radio Connection istriggered by the receipt of the request. In some aspects, the methodfurther includes receiving a Radio Connection Release message thatcomprises timing information that controls when a user terminal (UT) isto attempt a re-connection. In some aspects, the method further includesreceiving a Radio Connection Release message that comprises informationindicative of a forbidden area.

In an aspect of the disclosure, an apparatus for communication includesa memory and a processor coupled to the memory. The processor and thememory are configured to initiate a Radio Connection, and receive aRadio Connection Reject message after the initiation of the RadioConnection, where the Radio Connection Reject message includes anindication that the UT is to immediately attempt a reconnection.

In an aspect of the disclosure, an apparatus for communication includesmeans for initiating a Radio Connection, and means for receiving a RadioConnection Reject message after the initiating of the Radio Connection,where the Radio Connection Reject message includes an indication thatthe UT is to immediately attempt a reconnection.

In an aspect of the disclosure, a non-transitory computer-readablemedium storing computer-executable code includes code to: initiate aRadio Connection, and receive a Radio Connection Reject message afterthe initiation of the Radio Connection, where the Radio ConnectionReject message includes an indication that the UT is to immediatelyattempt a reconnection.

In some aspects, a method of communication includes initiating a RadioConnection, and receiving a Radio Connection Reject message after theinitiating of the Radio Connection, where the Radio Connection Rejectmessage includes a request for a user terminal (UT) to send old pagingarea code (PAC) information previously used by the UT. In some aspects,the request is to send the old PAC information in a Radio ConnectionRequest message. In some aspects, the initiating of the Radio Connectionincludes sending old PAC information. In some aspects, the initiating ofthe Radio Connection includes sending a PAC associated with a forbiddenpaging area (PA). In some aspects, the method further includes receivinga request to update PAC information, wherein the initiating of the RadioConnection is triggered by the receipt of the request. In some aspects,the method further includes receiving a Radio Connection Release messagethat comprises timing information that controls when a UT is to attempta re-connection. In some aspects, the method further includes receivinga Radio Connection Release message that comprises information indicativeof a forbidden area.

In an aspect of the disclosure, an apparatus for communication includesa memory and a processor coupled to the memory. The processor and thememory are configured to initiate a Radio Connection, and receive aRadio Connection Reject message after the initiation of the RadioConnection, where the Radio Connection Reject message includes a requestfor a UT to send old PAC information previously used by the UT.

In an aspect of the disclosure, an apparatus for communication includesmeans for initiating a Radio Connection, and means for receive a RadioConnection Reject message after the initiating of the Radio Connection,where the Radio Connection Reject message includes a request for a UT tosend old PAC information previously used by the UT.

In an aspect of the disclosure, a non-transitory computer-readablemedium storing computer-executable code includes code to: initiate aRadio Connection, and receive a Radio Connection Reject message afterthe initiation of the Radio Connection, where the Radio ConnectionReject message includes a request for a UT to send old PAC informationpreviously used by the UT.

In some aspects, a method of communication includes initiating a pagingarea code (PAC) update procedure, and sending a message comprising anold PAC previously used by a user terminal (UT). In some aspects, themessage is a Connection Request message. In some aspects, the messagefurther comprises a new PAC. In some aspects, the method furtherincludes initiating a Radio Connection.

In an aspect of the disclosure, an apparatus for communication includesa memory and a processor coupled to the memory. The processor and thememory are configured to initiate a paging area code (PAC) updateprocedure, and send a message comprising an old PAC previously used by aUT.

In an aspect of the disclosure, an apparatus for communication includesmeans for initiating a paging area code (PAC) update procedure, andmeans for sending a message comprising an old PAC previously used by aUT.

In an aspect of the disclosure, a non-transitory computer-readablemedium storing computer-executable code includes code to: initiate apaging area code (PAC) update procedure, and send a message comprisingan old PAC previously used by a UT.

The disclosure relates in some aspect to defining a reserved value forPAC (PACdefault). PACdefault may be used when an AxP assigned PAC is notavailable (e.g., when initiating an Attach procedure on “power on”, orafter a lapse of “service restriction for forbidden area”).

The disclosure relates in some aspect to assigning a new PAC andcommunicating it to the UT in a Radio Connection Reject messageindicating an immediate re-attempt. In addition, the message may includean optional indicator requesting the UT to send its old PAC in the nextRadio Connection Request.

In some aspects, a Radio Connection Reject may include a value of 0 fora waitTime field indicating that a UT is to “immediately re-attempt”reconnection. A Radio Connection Reject may include a field for a newPAC that is any valid PAC different from an old PAC. A Radio ConnectionReject may include a field that indicates whether an old PAC is needed(e.g., a value of TRUE or FALSE).

The disclosure relates in some aspect to sending an old PAC in a RadioConnection Request on request of an AxP (e.g., indicated to the UT in anold PAC needed field).

The disclosure relates in some aspect to sending a restriction duration,a restricted area definition, and a trigger for initiating a PAUprocedure in a Radio Connection Release message. The Radio ConnectionRelease may include, for example: a field for a Duration Threshold, afield for list of Restricted Areas, and a field for an indication thatan immediate update is required. The Duration Threshold may define theduration of a service restriction. Each restricted area in the list maybe defined as tuple of a GPS coordinate and a Distance around thatcoordinate. The Update Required field set to Immediate may forces a PAUprocedure with an invalid PAC value.

The disclosure relates in some aspect to assigning a UT to a forbiddenPAC (when the GPS location is false in a forbidden area) and sendingthis information in a Radio Connection Reconfiguration message. TheRadio Connection Reconfiguration message may include, for example: afield for a new PAC, a field for an indication that an update isrequired on release, and a field for a Location Change Threshold. Thefield for the new PAC may include, in some cases, any valid PAC valuefrom a forbidden PA set. The Update Required set to On Release mayinitiates a PAU procedure only after connection release. The LocationChange Threshold may allowing for fine tuning of a location thresholdfor idle mode and connected mode during a span of a Radio connection.

The disclosure relates in some aspect to requesting a connection releaseon completion of a UT location report procedure using an indicator in aLocation Indication message. The Location Indication message mayinclude, for example, a field for a Connection Release Indication (e.g.,a value of TRUE or FALSE). A value of TRUE may force an AxP to release aconnection.

The disclosure relates in some aspect to requesting a connection releasewith a Radio Connection Release Request message. The disclosure relatesin some aspect to requesting a UT location with a Location Requestmessage.

In an aspect of the disclosure, an apparatus for communication includesa memory and a processor coupled to the memory. The processor and thememory are configured to determine that a user terminal in idle mode isto be assigned paging area code (PAC) information, and conduct amobility operation using a default PAC as a result of the determination.

In an aspect of the disclosure, an apparatus for communication includesmeans for determining that a user terminal in idle mode is to beassigned paging area code (PAC) information, and means for conducting amobility operation using a default PAC as a result of the determination.

In an aspect of the disclosure, a non-transitory computer-readablemedium storing computer-executable code includes code to: determine thata user terminal in idle mode is to be assigned paging area code (PAC)information, and conduct a mobility operation using a default PAC as aresult of the determination.

In an aspect of the disclosure, an apparatus for communication includesa memory and a processor coupled to the memory. The processor and thememory are configured to initiate a Radio Connection, and receive aRadio Connection Reject message comprising paging area code (PAC)information after the initiating of the Radio Connection. In someaspects, the processor and the memory are further configured to receivea request to update PAC information, wherein the initiating of the RadioConnection is triggered by the receipt of the request. In some aspects,the processor and the memory are further configured to receive a RadioConnection Release message that comprises timing information thatcontrols when a user terminal (UT) is to attempt a re-connection. Insome aspects, the processor and the memory are further configured toreceive a Radio Connection Release message that comprises informationindicative of a forbidden area.

In an aspect of the disclosure, an apparatus for communication includesmeans for initiating a Radio Connection, and means for receiving a RadioConnection Reject message comprising paging area code (PAC) informationafter the initiating of the Radio Connection. In some aspects, theapparatus further includes means for receiving a request to update PACinformation, wherein the initiating of the Radio Connection is triggeredby the receipt of the request. In some aspects, the apparatus furtherincludes means for receiving a Radio Connection Release message thatcomprises timing information that controls when a user terminal (UT) isto attempt a re-connection. In some aspects, the apparatus furtherincludes means for receiving a Radio Connection Release message thatcomprises information indicative of a forbidden area.

In an aspect of the disclosure, a non-transitory computer-readablemedium storing computer-executable code includes code to: initiate aRadio Connection, and receive a Radio Connection Reject messagecomprising paging area code (PAC) information after the initiating ofthe Radio Connection. In some aspects, the computer-executable codefurther includes code to receive a request to update PAC information,wherein the initiating of the Radio Connection is triggered by thereceipt of the request. In some aspects, the computer-executable codefurther includes code to receive a Radio Connection Release message thatcomprises timing information that controls when a user terminal (UT) isto attempt a re-connection. In some aspects, the computer-executablecode further includes code to receive a Radio Connection Release messagethat comprises information indicative of a forbidden area.

In an aspect of the disclosure, an apparatus for communication includesa memory and a processor coupled to the memory. The processor and thememory are configured to initiate a Radio Connection, and receive aRadio Connection Reject message comprising an indication that the UT isto immediately attempt a reconnection after the initiating of the RadioConnection. In some aspects, the processor and the memory are furtherconfigured to receive a request to update PAC information, wherein theinitiating of the Radio Connection is triggered by the receipt of therequest. In some aspects, the processor and the memory are furtherconfigured to receive a Radio Connection Release message that comprisestiming information that controls when a user terminal (UT) is to attempta re-connection. In some aspects, the processor and the memory arefurther configured to receive a Radio Connection Release message thatcomprises information indicative of a forbidden area.

In an aspect of the disclosure, an apparatus for communication includesmeans for initiating a Radio Connection, and means for receiving a RadioConnection Reject message comprising an indication that the UT is toimmediately attempt a reconnection after the initiating of the RadioConnection. In some aspects, the apparatus further includes means forreceiving a request to update PAC information, wherein the initiating ofthe Radio Connection is triggered by the receipt of the request. In someaspects, the apparatus further includes means for receiving a RadioConnection Release message that comprises timing information thatcontrols when a user terminal (UT) is to attempt a re-connection. Insome aspects, the apparatus further includes means for receiving a RadioConnection Release message that comprises information indicative of aforbidden area.

In an aspect of the disclosure, a non-transitory computer-readablemedium storing computer-executable code includes code to: initiate aRadio Connection, and receive a Radio Connection Reject messagecomprising an indication that the UT is to immediately attempt areconnection after the initiating of the Radio Connection. In someaspects, the computer-executable code further includes code to receive arequest to update PAC information, wherein the initiating of the RadioConnection is triggered by the receipt of the request. In some aspects,the computer-executable code further includes code to receive a RadioConnection Release message that comprises timing information thatcontrols when a user terminal (UT) is to attempt a re-connection. Insome aspects, the computer-executable code further includes code toreceive a Radio Connection Release message that comprises informationindicative of a forbidden area.

In an aspect of the disclosure, an apparatus for communication includesa memory and a processor coupled to the memory. The processor and thememory are configured to initiate a Radio Connection, and receive aRadio Connection Reject message comprising a request for a UT to sendold PAC information previously used by the UT after the initiating ofthe Radio Connection. In some aspects, the processor and the memory arefurther configured to receive a request to update PAC information,wherein the initiating of the Radio Connection is triggered by thereceipt of the request. In some aspects, the processor and the memoryare further configured to receive a Radio Connection Release messagethat comprises timing information that controls when a user terminal(UT) is to attempt a re-connection. In some aspects, the processor andthe memory are further configured to receive a Radio Connection Releasemessage that comprises information indicative of a forbidden area.

In an aspect of the disclosure, an apparatus for communication includesmeans for initiating a Radio Connection, and means for receive a RadioConnection Reject message comprising a request for a UT to send old PACinformation previously used by the UT after the initiating of the RadioConnection. In some aspects, the apparatus further includes means forreceiving a request to update PAC information, wherein the initiating ofthe Radio Connection is triggered by the receipt of the request. In someaspects, the apparatus further includes means for receiving a RadioConnection Release message that comprises timing information thatcontrols when a user terminal (UT) is to attempt a re-connection. Insome aspects, the apparatus further includes means for receiving a RadioConnection Release message that comprises information indicative of aforbidden area.

In an aspect of the disclosure, a non-transitory computer-readablemedium storing computer-executable code includes code to: initiate aRadio Connection, and receive a Radio Connection Reject messagecomprising a request for a UT to send old PAC information previouslyused by the UT after the initiating of the Radio Connection. In someaspects, the computer-executable code further includes code to receive arequest to update PAC information, wherein the initiating of the RadioConnection is triggered by the receipt of the request. In some aspects,the computer-executable code further includes code to receive a RadioConnection Release message that comprises timing information thatcontrols when a user terminal (UT) is to attempt a re-connection. Insome aspects, the computer-executable code further includes code toreceive a Radio Connection Release message that comprises informationindicative of a forbidden area.

In an aspect of the disclosure, an apparatus for communication includesa memory and a processor coupled to the memory. The processor and thememory are configured to initiate a paging area code (PAC) updateprocedure, and send a message comprising an old PAC previously used by aUT. In some aspects, the processor and the memory are further configuredto initiate a Radio Connection.

In an aspect of the disclosure, an apparatus for communication includesmeans for initiating a paging area code (PAC) update procedure, andmeans for sending a message comprising an old PAC previously used by aUT. In some aspects, the apparatus further includes means for initiatinga Radio Connection.

In an aspect of the disclosure, a non-transitory computer-readablemedium storing computer-executable code includes code to: initiate apaging area code (PAC) update procedure, and send a message comprisingan old PAC previously used by a UT. In some aspects, thecomputer-executable code further includes code to initiate a RadioConnection.

In an aspect of the disclosure, an apparatus for communication includesa memory and a processor coupled to the memory. The processor and thememory are configured to determine that a user terminal (UT) is locatedwithin a forbidden area, and send a Radio Connection Reconfigurationmessage to the UT as a result of the determination, wherein the RadioConnection Reconfiguration message includes a paging area codeassociated with the forbidden area for the UT. In some aspects, theprocessor and the memory are further configured to receive a RadioConnection Release message that comprises a request to initiate a CoreNetwork Control Layer update procedure after sending a Radio ConnectionReconfiguration message, and initiate the Core Network Control Layerupdate procedure as a result of receiving the Radio Connection Releasemessage.

In an aspect of the disclosure, an apparatus for communication includesmeans for determining that a user terminal (UT) is located within aforbidden area, and means for sending a Radio Connection Reconfigurationmessage to the UT as a result of the determination, wherein the RadioConnection Reconfiguration message includes a paging area codeassociated with the forbidden area for the UT. In some aspects, theapparatus further includes means for receiving a Radio ConnectionRelease message that comprises a request to initiate a Core NetworkControl Layer update procedure after sending a Radio ConnectionReconfiguration message, and means for initiating the Core NetworkControl Layer update procedure as a result of receiving the RadioConnection Release message.

In an aspect of the disclosure, a non-transitory computer-readablemedium storing computer-executable code includes code to: determine thata user terminal (UT) is located within a forbidden area, and send aRadio Connection Reconfiguration message to the UT as a result of thedetermination, wherein the Radio Connection Reconfiguration messageincludes a paging area code associated with the forbidden area for theUT. In some aspects, the computer-executable code further includes codeto receive a Radio Connection Release message that comprises a requestto initiate a Core Network Control Layer update procedure after sendinga Radio Connection Reconfiguration message, and initiate the CoreNetwork Control Layer update procedure as a result of receiving theRadio Connection Release message.

In an aspect of the disclosure, an apparatus for communication includesa memory and a processor coupled to the memory. The processor and thememory are configured to receive location information for a userterminal (UT), determine, based on the location information, a proximityof the UT to a forbidden area, and define a location reporting thresholdfor the UT based on the determination. In some aspects, the processorand the memory are further configured to send the location reportingthreshold to the UT via a Radio Connection Reconfiguration message.

In an aspect of the disclosure, an apparatus for communication includesmeans for receiving location information for a user terminal (UT), meansfor determining, based on the location information, a proximity of theUT to a forbidden area, and means for defining a location reportingthreshold for the UT based on the determination. In some aspects, theapparatus further includes means for sending the location reportingthreshold to the UT via a Radio Connection Reconfiguration message.

In an aspect of the disclosure, a non-transitory computer-readablemedium storing computer-executable code includes code to: receivelocation information for a user terminal (UT), determine, based on thelocation information, a proximity of the UT to a forbidden area, anddefine a location reporting threshold for the UT based on thedetermination. send the location reporting threshold to the UT via aRadio Connection Reconfiguration message. In some aspects, thecomputer-executable code further includes code to send the locationreporting threshold to the UT via a Radio Connection Reconfigurationmessage.

In an aspect of the disclosure, an apparatus for communication includesa memory and a processor coupled to the memory. The processor and thememory are configured to determine that a service restriction no longerapplies for a user terminal (UT), and conduct a mobility operation usinga default paging area code (PAC) as a result of the determination.

In an aspect of the disclosure, an apparatus for communication includesmeans for determining that a service restriction no longer applies for auser terminal (UT), and means for conducting a mobility operation usinga default paging area code (PAC) as a result of the determination

In an aspect of the disclosure, a non-transitory computer-readablemedium storing computer-executable code includes code to: determine thata service restriction no longer applies for a user terminal (UT), andconduct a mobility operation using a default paging area code (PAC) as aresult of the determination

In an aspect of the disclosure, an apparatus for communication includesa memory and a processor coupled to the memory. The processor and thememory are configured to determine that a trigger condition has occurredat a user terminal (UT), and send a request, from the UT, to release aconnection as a result of the determination. In some aspects, theprocessor and the memory are further configured to send the locationinformation for the UT, wherein the location information is sent inconjunction with the request to release the connection.

In an aspect of the disclosure, an apparatus for communication includesmeans for determining that a trigger condition has occurred at a userterminal (UT), and means for sending a request, from the UT, to releasea connection as a result of the determination. In some aspects, theapparatus further includes means for sending the location informationfor the UT, wherein the location information is sent in conjunction withthe request to release the connection.

In an aspect of the disclosure, a non-transitory computer-readablemedium storing computer-executable code includes code to: determine thata trigger condition has occurred at a user terminal (UT), and send arequest, from the UT, to release a connection as a result of thedetermination. In some aspects, the computer-executable code furtherincludes code to send the location information for the UT, wherein thelocation information is sent in conjunction with the request to releasethe connection.

In an aspect of the disclosure, a method of communication includesdetermining that a user terminal in idle mode is to be assigned pagingarea code (PAC) information, and conducting a mobility operation using adefault PAC as a result of the determination. In some aspects, theconducting of the mobility operation includes initiating a Registerprocedure, and initiating a Radio Connection without sending any PACinformation. In some aspects, the default paging area code is excludedfrom a set of paging area codes used for paging area update operations.In some aspects, the default paging area code is used between a CoreNetwork Control Layer and a Radio Connection Layer internal to a userterminal (UT). In some aspects, the default paging area code is not sentin any signaling messages over-the-air.

In an aspect of the disclosure, a method of communication includesdetermining that paging area code (PAC) information is to be sent to auser terminal (UT), and communicating the PAC information to the UT. Insome aspects, the determination that the PAC information is to be sentto the UT includes determining that the UT needs an initial PACassignment. In some aspects, the determination that the PAC informationis to be sent to the UT includes determining that the UT needs a PACreassignment. In some aspects, the determination that the UT needs a PACreassignment is based on load balancing. In some aspects, the PACinformation is communicated via a Radio Connection Reject message. Insome aspects, the Radio Connection Reject message includes an indicationthat the UT is to immediately attempt a reconnection. In some aspects,the Radio Connection Reject message includes a request for the UT tosend old PAC information in a Radio Connection Request. In some aspects,the method further includes using a receiving UT location report todetermine whether to accept or reject the UT. In some aspects, thepaging area information is communicated via a Radio Connection Requestmessage. In some aspects, the paging area information is communicatedvia a Radio Connection Reconfiguration message for a non-handoffscenario. In some aspects, the Radio Connection Reconfiguration messageincludes timing information that controls when the UT is to attemptreconfiguration.

In an aspect of the disclosure, a method of communication includesinitiating a Radio Connection, and receiving a message comprising pagingarea code (PAC) information after the initiating of the RadioConnection. In some aspects, the message includes a Radio ConnectionReject message. In some aspects, the Radio Connection Reject messageincludes timing information that controls when the UT can attempt areconnection. In some aspects, the Radio Connection Reject messageincludes a request for the UT to send old PAC information in a RadioConnection Request message. In some aspects, the message includes aRadio Connection Request message. In some aspects, the message includesa Radio Connection Reconfiguration message. In some aspects, the RadioConnection Reconfiguration message includes timing information thatcontrols when a user terminal (UT) is to attempt reconfiguration. Insome aspects, the initiating of the Radio Connection includes sendingold PAC information. In some aspects, the initiating of the RadioConnection includes sending a PAC associated with a forbidden pagingarea (PA). In some aspects, the method further includes receiving arequest to update PAC information, wherein the initiating of the RadioConnection is triggered by the receipt of the request. In some aspects,the method further includes receiving a Radio Connection Release messagethat includes timing information that controls when a user terminal (UT)is to attempt a re-connection. In some aspects, the method furtherincludes receiving a Radio Connection Release message that includesinformation indicative of a forbidden area.

In an aspect of the disclosure, a method of communication includesdetermining that a user terminal (UT) is located within a forbiddenarea, and sending a Radio Connection Release message to the UT as aresult of the determination. In some aspects, the Radio ConnectionRelease message includes a request to initiate a Core Network ControlLayer update procedure. In some aspects, the Radio Connection Releasemessage includes timing information that controls when the UT is toattempt reconfiguration. In some aspects, the Radio Connection Releasemessage includes information indicative of the forbidden area.

In an aspect of the disclosure, a method of communication includesreceiving a Radio Connection Release message that includes a request toinitiate a Core Network Control Layer update procedure, and initiatingthe Core Network Control Layer update procedure as a result of receivingthe Radio Connection Release message. In some aspects, the RadioConnection Release message further includes timing information thatcontrols when the UT is to attempt reconfiguration. In some aspects, theRadio Connection Release message further includes information indicativeof a forbidden area. In some aspects, the Core Network Control Layerupdate procedure includes sending a forbidden paging area code (PAC).

In an aspect of the disclosure, a method of communication includesreceiving location information for a user terminal (UT), determining,based on the location information, a probability of the UT being in aforbidden area, and defining a location reporting threshold for the UTbased on the determination. In some aspects, the method further includessending the location reporting threshold to the UT via a RadioConnection Reconfiguration message. In some aspects, the locationreporting threshold includes a distance threshold. In some aspects, thelocation reporting threshold includes a duration threshold. In someaspects, the determination includes determining that the UE is near theforbidden area. In some aspects, the determination includes determiningthat the UE is in the forbidden area.

In an aspect of the disclosure, a method of communication includesdetermining that a service restriction no longer applies for a userterminal (UT), and conducting a mobility operation using a defaultpaging area code (PAC) as a result of the determination. In someaspects, the conducting of the mobility operation includes initiating aRegister procedure, and initiating a Radio Connection without sendingany PAC information. In some aspects, the default paging area code isexcluded from a set of paging area codes used for paging area updateoperations. In some aspects, the default paging area code is usedbetween a Core Network Control Layer and a Radio Connection Layerinternal to a user terminal (UT). In some aspects, the default pagingarea code is not sent in any signaling messages over-the-air.

In an aspect of the disclosure, a method of communication includesdetermining that a user terminal (UT) will enter idle mode afterreporting location information for the UT, and sending the locationinformation for the UT, wherein the location information is sent inconjunction with a request to release a connection. In some aspects, theconnection is a Radio Connection for the UT. In some aspects, theconnection is a Core Network Interface connection.

In an aspect of the disclosure, a method of communication includesdetermining that a trigger condition has occurred at a user terminal(UT), and sending a request, from the UT, to release a connection as aresult of the determination. In some aspects, the determination that thetrigger condition has occurred includes determining that the network hascompleted downloading of satellite transition information. In someaspects, the determination that the trigger condition has occurredincludes determining that the UT has completed sending of locationinformation. In some aspects, the determination that the triggercondition has occurred includes determining that the UT will transitionto idle mode. In some aspects, the determination that the triggercondition has occurred includes determining that a procedure for whichthe connection was established has completed. In some aspects, theconnection is a Radio Connection for the UT. In some aspects, theconnection is a Core Network Interface connection.

In an aspect of the disclosure, a method of communication includesdetermining that location information for a user terminal (UT) isneeded, and sending a request for the location information as a resultof the determination. In some aspects, the method is performed bycontrol processor of a ground network. In some aspects, the method isperformed by traffic processor of a ground network.

In an aspect of the disclosure, an apparatus for communication includesa memory and a processor coupled to the memory. The processor and thememory are configured to determine that a user terminal in idle mode isto be assigned paging area code (PAC) information, and conduct amobility operation using a default PAC as a result of the determination.In some aspects, the conducting of the mobility operation includesinitiating a Register procedure, initiating a Radio Connection withoutsending any PAC information. In some aspects, the default paging areacode is excluded from a set of paging area codes used for paging areaupdate operations. In some aspects, the default paging area code is usedbetween a Core Network Control Layer and a Radio Connection Layerinternal to a user terminal (UT). In some aspects, the default pagingarea code is not sent in any signaling messages over-the-air.

In an aspect of the disclosure, an apparatus for communication includesa memory and a processor coupled to the memory. The processor and thememory are configured to determine that paging area code (PAC)information is to be sent to a user terminal (UT), and communicate thePAC information to the UT. In some aspects, the determination that thePAC information is to be sent to the UT includes determining that the UTneeds an initial PAC assignment. In some aspects, the determination thatthe PAC information is to be sent to the UT includes determining thatthe UT needs a PAC reassignment. In some aspects, the determination thatthe UT needs a PAC reassignment is based on load balancing. In someaspects, the PAC information is communicated via a Radio ConnectionReject message. In some aspects, the Radio Connection Reject messageincludes an indication that the UT is to immediately attempt areconnection. In some aspects, the Radio Connection Reject messageincludes a request for the UT to send old PAC information in a RadioConnection Request. In some aspects, the processor and the memory arefurther configured to use a receiving UT location report to determinewhether to accept or reject the UT. In some aspects, the paging areainformation is communicated via a Radio Connection Request message. Insome aspects, the paging area information is communicated via a RadioConnection Reconfiguration message for a non-handoff scenario. In someaspects, the Radio Connection Reconfiguration message includes timinginformation that controls when the UT is to attempt reconfiguration.

In an aspect of the disclosure, an apparatus for communication includesa memory and a processor coupled to the memory. The processor and thememory are configured to initiate a Radio Connection, and receive amessage comprising paging area code (PAC) information after theinitiating of the Radio Connection. In some aspects, the messageincludes a Radio Connection Reject message. In some aspects, the RadioConnection Reject message includes timing information that controls whenthe UT can attempt a reconnection. In some aspects, the Radio ConnectionReject message includes a request for the UT to send old PAC informationin a Radio Connection Request message. In some aspects, the messageincludes a Radio Connection Request message. In some aspects, themessage includes a Radio Connection Reconfiguration message. In someaspects, the Radio Connection Reconfiguration message includes timinginformation that controls when a user terminal (UT) is to attemptreconfiguration. In some aspects, the initiating of the Radio Connectionincludes sending old PAC information. In some aspects, the initiating ofthe Radio Connection includes sending a PAC associated with a forbiddenpaging area (PA). In some aspects, the processor and the memory arefurther configured to receive a request to update PAC information, andthe initiating of the Radio Connection is triggered by the receipt ofthe request. In some aspects, the processor and the memory are furtherconfigured to receive a Radio Connection Release message that includestiming information that controls when a user terminal (UT) is to attempta re-connection. In some aspects, the processor and the memory arefurther configured to receive a Radio Connection Release message thatincludes information indicative of a forbidden area.

In an aspect of the disclosure, an apparatus for communication includesa memory and a processor coupled to the memory. The processor and thememory are configured to determine that a user terminal (UT) is locatedwithin a forbidden area, and send a Radio Connection Release message tothe UT as a result of the determination. In some aspects, the RadioConnection Release message includes a request to initiate a Core NetworkControl Layer update procedure. In some aspects, the Radio ConnectionRelease message includes timing information that controls when the UT isto attempt reconfiguration. In some aspects, the Radio ConnectionRelease message includes information indicative of the forbidden area.

In an aspect of the disclosure, an apparatus for communication includesa memory and a processor coupled to the memory. The processor and thememory are configured to receive a Radio Connection Release message thatincludes a request to initiate a Core Network Control Layer updateprocedure, and initiate the Core Network Control Layer update procedureas a result of receiving the Radio Connection Release message. In someaspects, the Radio Connection Release message further includes timinginformation that controls when the UT is to attempt reconfiguration. Insome aspects, the Radio Connection Release message further includesinformation indicative of a forbidden area. In some aspects, the CoreNetwork Control Layer update procedure includes sending a forbiddenpaging area code (PAC).

In an aspect of the disclosure, an apparatus for communication includesa memory and a processor coupled to the memory. The processor and thememory are configured to receive location information for a userterminal (UT), determine, based on the location information, aprobability of the UT being in a forbidden area, and define a locationreporting threshold for the UT based on the determination. In someaspects, the processor and the memory are further configured to send thelocation reporting threshold to the UT via a Radio ConnectionReconfiguration message. In some aspects, the location reportingthreshold includes a distance threshold. In some aspects, the locationreporting threshold includes a duration threshold. In some aspects, thedetermination includes determining that the UE is near the forbiddenarea. In some aspects, the determination includes determining that theUE is in the forbidden area.

In an aspect of the disclosure, an apparatus for communication includesa memory and a processor coupled to the memory. The processor and thememory are configured to determine that a service restriction no longerapplies for a user terminal (UT), and conduct a mobility operation usinga default paging area code (PAC) as a result of the determination. Insome aspects, the conducting of the mobility operation includesinitiating a Register procedure, and initiating a Radio Connectionwithout sending any PAC information. In some aspects, the default pagingarea code is excluded from a set of paging area codes used for pagingarea update operations. In some aspects, the default paging area code isused between a Core Network Control Layer and a Radio Connection Layerinternal to a user terminal (UT). In some aspects, the default pagingarea code is not sent in any signaling messages over-the-air.

In an aspect of the disclosure, an apparatus for communication includesa memory and a processor coupled to the memory. The processor and thememory are configured to determine that a user terminal (UT) will enteridle mode after reporting location information for the UT, and send thelocation information for the UT, wherein the location information issent in conjunction with a request to release a connection. In someaspects, the connection is a Radio Connection for the UT. In someaspects, the connection is a Core Network Interface connection.

In an aspect of the disclosure, an apparatus for communication includesa memory and a processor coupled to the memory. The processor and thememory are configured to determine that a trigger condition has occurredat a user terminal (UT), and send a request, from the UT, to release aconnection as a result of the determination. In some aspects, thedetermination that the trigger condition has occurred includesdetermining that the network has completed downloading of satellitetransition information. In some aspects, the determination that thetrigger condition has occurred includes determining that the UT hascompleted sending of location information. In some aspects, thedetermination that the trigger condition has occurred includesdetermining that the UT will transition to idle mode. In some aspects,the determination that the trigger condition has occurred includesdetermining that a procedure for which the connection was establishedhas completed. In some aspects, the connection is a Radio Connection forthe UT. In some aspects, the connection is a Core Network Interfaceconnection.

In an aspect of the disclosure, an apparatus for communication includesa memory and a processor coupled to the memory. The processor and thememory are configured to determine that location information for a userterminal (UT) is needed, and send a request for the location informationas a result of the determination. In some aspects, the apparatus is acontrol processor of a ground network. In some aspects, the apparatus isa traffic processor of a ground network.

In an aspect of the disclosure, an apparatus for communication includesmeans for determining that a user terminal in idle mode is to beassigned paging area code (PAC) information, and means for conducting amobility operation using a default PAC as a result of the determination.

In an aspect of the disclosure, an apparatus for communication includesmeans for determining that paging area code (PAC) information is to besent to a user terminal (UT), and means for communicating the PACinformation to the UT. In some aspects, the apparatus further includesmeans for using a receiving UT location report to determine whether toaccept or reject the UT.

In an aspect of the disclosure, an apparatus for communication includesmeans for initiating a Radio Connection, and means for receiving amessage comprising paging area code (PAC) information after theinitiating of the Radio Connection. In some aspects, the apparatusfurther includes means for receiving a request to update PACinformation, wherein the initiating of the Radio Connection is triggeredby the receipt of the request. In some aspects, the apparatus furtherincludes means for receiving a Radio Connection Release message thatincludes timing information that controls when a user terminal (UT) isto attempt a re-connection. In some aspects, the apparatus furtherincludes means for receiving a Radio Connection Release message thatincludes information indicative of a forbidden area.

In an aspect of the disclosure, an apparatus for communication includesmeans for determining that a user terminal (UT) is located within aforbidden area, and means for sending a Radio Connection Release messageto the UT as a result of the determination.

In an aspect of the disclosure, an apparatus for communication includesmeans for receiving a Radio Connection Release message that includes arequest to initiate a Core Network Control Layer update procedure, andmeans for initiating the Core Network Control Layer update procedure asa result of receiving the Radio Connection Release message.

In an aspect of the disclosure, an apparatus for communication includesmeans for receiving location information for a user terminal (UT), meansfor determining, based on the location information, a probability of theUT being in a forbidden area, and means for defining a locationreporting threshold for the UT based on the determination. In someaspects, the apparatus further includes means for sending the locationreporting threshold to the UT via a Radio Connection Reconfigurationmessage.

In an aspect of the disclosure, an apparatus for communication includesmeans for determining that a service restriction no longer applies for auser terminal (UT), and means for conducting a mobility operation usinga default paging area code (PAC) as a result of the determination.

In an aspect of the disclosure, an apparatus for communication includesmeans for determining that a user terminal (UT) will enter idle modeafter reporting location information for the UT, and means for sendingthe location information for the UT, wherein the location information issent in conjunction with a request to release a connection.

In an aspect of the disclosure, an apparatus for communication includesmeans for determining that a trigger condition has occurred at a userterminal (UT), and means for sending a request, from the UT, to releasea connection as a result of the determination.

In an aspect of the disclosure, an apparatus for communication includesmeans for determining that location information for a user terminal (UT)is needed, and means for sending a request for the location informationas a result of the determination.

In an aspect of the disclosure, a non-transitory computer-readablemedium storing computer-executable code, includes code to determine thata user terminal in idle mode is to be assigned paging area code (PAC)information, and conduct a mobility operation using a default PAC as aresult of the determination.

In an aspect of the disclosure, a non-transitory computer-readablemedium storing computer-executable code, includes code to determine thatpaging area code (PAC) information is to be sent to a user terminal(UT), and communicate the PAC information to the UT.

In an aspect of the disclosure, a non-transitory computer-readablemedium storing computer-executable code, includes code to initiate aRadio Connection, and receive a message comprising paging area code(PAC) information after the initiating of the Radio Connection.

In an aspect of the disclosure, a non-transitory computer-readablemedium storing computer-executable code, includes code to determine thata user terminal (UT) is located within a forbidden area, and send aRadio Connection Release message to the UT as a result of thedetermination.

In an aspect of the disclosure, a non-transitory computer-readablemedium storing computer-executable code, includes code to receive aRadio Connection Release message that includes a request to initiate aCore Network Control Layer update procedure, and initiate the CoreNetwork Control Layer update procedure as a result of receiving theRadio Connection Release message.

In an aspect of the disclosure, a non-transitory computer-readablemedium storing computer-executable code, includes code to receivelocation information for a user terminal (UT), determine, based on thelocation information, a probability of the UT being in a forbidden area,and define a location reporting threshold for the UT based on thedetermination.

In an aspect of the disclosure, a non-transitory computer-readablemedium storing computer-executable code, includes code to determine thata service restriction no longer applies for a user terminal (UT), andconduct a mobility operation using a default paging area code (PAC) as aresult of the determination.

In an aspect of the disclosure, a non-transitory computer-readablemedium storing computer-executable code, includes code to determine thata user terminal (UT) will enter idle mode after reporting locationinformation for the UT, and send the location information for the UT,wherein the location information is sent in conjunction with a requestto release a connection.

In an aspect of the disclosure, a non-transitory computer-readablemedium storing computer-executable code, includes code to determine thata trigger condition has occurred at a user terminal (UT), and send arequest, from the UT, to release a connection as a result of thedetermination.

In an aspect of the disclosure, a non-transitory computer-readablemedium storing computer-executable code, includes code to determine thatlocation information for a user terminal (UT) is needed, and send arequest for the location information as a result of the determination.

XIV. Additional Aspects

Many aspects are described in terms of sequences of actions to beperformed by, for example, elements of a computing device. It will berecognized that various actions described herein can be performed byspecific circuits, for example, central processing units (CPUs), graphicprocessing units (GPUs), digital signal processors (DSPs),application-specific integrated circuits (ASICs), field programmablegate arrays (FPGAs), or various other types of general purpose orspecial purpose processors or circuits, by program instructions beingexecuted by one or more processors, or by a combination of both.Additionally, these sequence of actions described herein can beconsidered to be embodied entirely within any form of computer readablestorage medium having stored therein a corresponding set of computerinstructions that upon execution would cause an associated processor toperform the functionality described herein. Thus, the various aspects ofthe disclosure may be embodied in a number of different forms, all ofwhich have been contemplated to be within the scope of the claimedsubject matter. In addition, for each of the aspects described herein,the corresponding form of any such aspects may be described herein as,for example, “logic configured to” perform the described action.

Those of skill in the art will appreciate that information and signalsmay be represented using any of a variety of different technologies andtechniques. For example, data, instructions, commands, information,signals, bits, symbols, and chips that may be referenced throughout theabove description may be represented by voltages, currents,electromagnetic waves, magnetic fields or particles, optical fields orparticles, or any combination thereof.

Further, those of skill in the art will appreciate that the variousillustrative logical blocks, modules, circuits, and algorithm stepsdescribed in connection with the aspects disclosed herein may beimplemented as electronic hardware, computer software, or combinationsof both. To clearly illustrate this interchangeability of hardware andsoftware, various illustrative components, blocks, modules, circuits,and steps have been described above generally in terms of theirfunctionality. Whether such functionality is implemented as hardware orsoftware depends upon the particular application and design constraintsimposed on the overall system. Skilled artisans may implement thedescribed functionality in varying ways for each particular application,but such implementation decisions should not be interpreted as causing adeparture from the scope of the disclosure.

One or more of the components, steps, features and/or functionsillustrated in above may be rearranged and/or combined into a singlecomponent, step, feature or function or embodied in several components,steps, or functions. Additional elements, components, steps, and/orfunctions may also be added without departing from novel featuresdisclosed herein. The apparatus, devices, and/or components illustratedabove may be configured to perform one or more of the methods, features,or steps described herein. The novel algorithms described herein mayalso be efficiently implemented in software and/or embedded in hardware.

It is to be understood that the specific order or hierarchy of steps inthe methods disclosed is an illustration of example processes. Basedupon design preferences, it is understood that the specific order orhierarchy of steps in the methods may be rearranged. The accompanyingmethod claims present elements of the various steps in a sample order,and are not meant to be limited to the specific order or hierarchypresented unless specifically recited therein.

The methods, sequences or algorithms described in connection with theaspects disclosed herein may be embodied directly in hardware, in asoftware module executed by a processor, or in a combination of the two.A software module may reside in RAM memory, flash memory, ROM memory,EPROM memory, EEPROM memory, registers, hard disk, a removable disk, aCD-ROM, or any other form of storage medium known in the art. An exampleof a storage medium is coupled to the processor such that the processorcan read information from, and write information to, the storage medium.In the alternative, the storage medium may be integral to the processor.

The word “exemplary” is used herein to mean “serving as an example,instance, or illustration.” Any aspect described herein as “exemplary”is not necessarily to be construed as preferred or advantageous overother aspects. Likewise, the term “aspects” does not require that allaspects include the discussed feature, advantage or mode of operation.

The terminology used herein is for the purpose of describing particularaspects only and is not intended to be limiting of the aspects. As usedherein, the singular forms “a,” “an” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will be further understood that the terms “comprises,”“comprising,” “includes” or “including,” when used herein, specify thepresence of stated features, integers, steps, operations, elements, orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components, orgroups thereof. Moreover, it is understood that the word “or” has thesame meaning as the Boolean operator “OR,” that is, it encompasses thepossibilities of “either” and “both” and is not limited to “exclusiveor” (“XOR”), unless expressly stated otherwise. It is also understoodthat the symbol “/” between two adjacent words has the same meaning as“or” unless expressly stated otherwise. Moreover, phrases such as“connected to,” “coupled to” or “in communication with” are not limitedto direct connections unless expressly stated otherwise.

Any reference to an element herein using a designation such as “first,”“second,” and so forth does not generally limit the quantity or order ofthose elements. Rather, these designations may be used herein as aconvenient method of distinguishing between two or more elements orinstances of an element. Thus, a reference to first and second elementsdoes not mean that only two elements may be used there or that the firstelement must precede the second element in some manner. Also, unlessstated otherwise a set of elements may comprise one or more elements. Inaddition, terminology of the form “at least one of a, b, or c” or “a, b,c, or any combination thereof” used in the description or the claimsmeans “a or b or c or any combination of these elements.” For example,this terminology may include a, or b, or c, or a and b, or a and c, or aand b and c, or 2 a, or 2 b, or 2 c, or 2 a and b, and so on.

As used herein, the term “determining” encompasses a wide variety ofactions. For example, “determining” may include calculating, computing,processing, deriving, investigating, looking up (e.g., looking up in atable, a database or another data structure), ascertaining, and thelike. Also, “determining” may include receiving (e.g., receivinginformation), accessing (e.g., accessing data in a memory), and thelike. Also, “determining” may include resolving, selecting, choosing,establishing, and the like.

While the foregoing disclosure shows illustrative aspects, it should benoted that various changes and modifications could be made hereinwithout departing from the scope of the appended claims. The functions,steps or actions of the method claims in accordance with aspectsdescribed herein need not be performed in any particular order unlessexpressly stated otherwise. Furthermore, although elements may bedescribed or claimed in the singular, the plural is contemplated unlesslimitation to the singular is explicitly stated.

1. A method of communication, comprising: determining that a userterminal is located within a forbidden area; and sending a RadioConnection Reconfiguration message to the user terminal as a result ofthe determination, wherein the Radio Connection Reconfiguration messageincludes a paging area code associated with the forbidden area for theuser terminal.
 2. The method of claim 1, further comprising: sending aRadio Connection Release message after sending the Radio ConnectionReconfiguration message, wherein the Radio Connection Release messagecomprises a request to initiate a Core Network Control Layer updateprocedure.
 3. The method of claim 2, wherein the Core Network ControlLayer update procedure includes sending a forbidden paging area code. 4.The method of claim 2, wherein the Radio Connection Release messagecomprises a request to immediately initiate the Core Network ControlLayer update procedure.
 5. The method of claim 2, wherein the RadioConnection Release message comprises timing information that controlswhen the user terminal is to attempt reconfiguration.
 6. The method ofclaim 2, wherein the Radio Connection Release message comprisesinformation indicative of the forbidden area.
 7. The method of claim 6,wherein the information indicative of the forbidden area comprises anellipsoid point and a distance from the ellipsoid point.
 8. The methodof claim 1, further comprising: receiving location information from theuser terminal, wherein the determination is based on the receivedlocation information.
 9. The method of claim 1, further comprising:determining that location information for the user terminal is needed;and sending a request for the location information as a result of thedetermination that location information for the user terminal is needed.10. The method of claim 1, wherein the method is performed by asatellite ground network. 11-21. (canceled)
 22. A method ofcommunication, comprising: receiving location information for a userterminal; determining, based on the location information, a proximity ofthe user terminal to a forbidden area; and defining a location reportingthreshold for the user terminal based on the determination.
 23. Themethod of claim 22, further comprising: sending the location reportingthreshold to the user terminal.
 24. The method of claim 22, furthercomprising: sending the location reporting threshold to the userterminal via a Radio Connection Reconfiguration message.
 25. The methodof claim 22, wherein the location reporting threshold comprises adistance threshold.
 26. The method of claim 22, wherein the locationreporting threshold comprises a duration threshold.
 27. The method ofclaim 22, wherein the determination comprises determining that the userterminal is near the forbidden area.
 28. The method of claim 22, whereinthe determination comprises determining that the user terminal is in theforbidden area. 29-37. (canceled)
 38. A method of communication,comprising: determining that a service restriction for a user terminalhas ended; and conducting a mobility operation using a default pagingarea code as a result of the determination.
 39. The method of claim 38,wherein the conducting of the mobility operation comprises: initiating aRadio Connection.
 40. The method of claim 38, wherein the conducting ofthe mobility operation comprises: initiating a Radio Connection withoutsending any paging area code information for the initiation of the RadioConnection.
 41. The method of claim 38, wherein the default paging areacode is excluded from a set of paging area codes used for paging areaupdate operations. 42-48. (canceled)
 49. A method of communication,comprising: determining that a trigger condition has occurred at a userterminal; and sending a request, from the user terminal, to release aconnection as a result of the determination.
 50. The method of claim 49,wherein the determination that the trigger condition has occurredcomprises determining that the user terminal will enter idle mode afterreporting location information for the user terminal.
 51. The method ofclaim 50, further comprising: sending the location information for theuser terminal, wherein the location information is sent in conjunctionwith the request to release the connection.
 52. The method of claim 49,wherein the determination that the trigger condition has occurredcomprises determining that a network has completed downloading ofsatellite transition information.
 53. The method of claim 49, whereinthe determination that the trigger condition has occurred comprisesdetermining that the user terminal has completed sending of locationinformation.
 54. The method of claim 49, wherein the determination thatthe trigger condition has occurred comprises determining that the userterminal will transition to an idle mode.
 55. The method of claim 49,wherein the determination that the trigger condition has occurredcomprises determining that a procedure for which the connection wasestablished has completed.
 56. The method of claim 49, wherein theconnection is a Radio Connection for the user terminal.
 57. The methodof claim 49, wherein the connection is a Core Network Interfaceconnection. 58-67. (canceled)